際際滷

際際滷Share a Scribd company logo

Aria interview questions

Download as DOCX, PDF
L
learnstraightsap

The document contains a list of interview questions related to accessibility and ARIA. The questions cover topics such as who benefits from accessibility, defining inclusive design, examples of assistive technologies, the purpose of heading elements, skip links, tools for testing accessibility, plain language benefits, appropriate uses of links and buttons, indicating elements' states without visuals, carousel accessibility issues, text resize considerations, the accessibility tree, and more.

1 of 4
Download to read offline
ARIA Interview Questions: Who benefits from accessibility? How would you define inclusive and/or universaldesign? o Can you providean example? (does not need to be web related) How has your approach to accessibility changed over time? Name some ways responsive/mobilefirstdesign can affect accessibility. What are someuser experience (UX) concerns to be awareof when using iconography in user interfaces (UI)? What assistivetechnologies (ATs) are you familiar with (desktop + mobile)? o What do you feel is your skilllevel with these AT(s)? Describethe purposeof heading and header elements, and how they are usefulin websites and web applications. What are skip links? o How can users benefit fromthem? o What are someof their limitations? What are someof the tools available to test the accessibility of a website or web application? How can using plain languagebenefit the accessibility of a project? Describeappropriateinstances to usea link, vs a generic button, vs a submit button. Describeways to indicate an element or components state that arent entirely reliant on visuals. How can carousels be problematic for users with disabilities? What are somedesign considerations for supporting text resize/zoomon web? Mobile apps? In whatways can the CSS display property affectthe accessibility of a document? What is the difference between legend and label elements? What is the purposeof the alt attribute for images? o Can you describe the effect of an empty alt, or the lack of the attribute, on an image? o In whatinstances might an empty alt or no alt be appropriate? o How might alternative text for an image vary, depending on the context the image is used in?
o Since svgs dontaccept the alt attribute, how can one provide alternative text for these graphics? What methods would you use to find an elements accessible name? What is the accessibility tree? Why are rems or ems preferableto pixels for setting type size? Why is it important to allow the viewportto scale? How is the title attribute exposed to assistivetechnologies? o What kind of elements can title attributes be used on? o What sortof information is appropriatefor usewith the title attribute? Describea scenario where you might need to use aria-describedby. What are landmark roles and how can they be useful? For each element, when might you use a toggle button, a switch control, or a checkbox? Describemethods to hide content: o Fromall users. o Fromonly screen reader users. o Fromsighted users, butnot screen reader users. o And why you might do so. Is it possibleto overuseARIA in a website? Explain why or why not. Aside fromscreen readers, What other assistivetechnologies can be affected by useof ARIA? How? What is the difference between hidden, aria-hidden="true" and role="presentation" or role="none"? Describeinstances where you might need to use aria-live. o What values (such as assertiveor polite) might you give the attribute in different situations? How would you mark-up an icon font or SVG that was for decorative purposes? How is CSS pseudo content treated by screen readers?
Describethe steps you take in reviewing or auditing a website or application for accessibility? Describean instance wherean automated test would not flag a blatant accessibility error? When should you use or recommend ARIA roles or attributes to solvean accessibility issue? Describeyour process for figuring out if an accessibility bug is due to a developer, browser, or assistivetechnology error? Describeyour thoughts on how a single page web app should handle focus when a new screen loads. Name an ARIA attribute that requires either a child/parent relationship or a pairing role. What is your understanding of accessiblename computation and how it affects modifying the way screen readers announce certain content? What are someissues with modifying normal scrolling behavior? For example: infinite scrolling or scrolljacking. Design Talk about the pros and cons of flat and skeuomorphic design trends in regards to accessibility. Explain the importance of color contrastin designing for inclusion. Besides :hover, name other states an actionable element (links, buttons, formcontrols, etc.) could havestyles for, and why providing them is important? When might it be appropriateto removethe visualoutline froma focused element? If a formor formfield were to return an error message, wheremight you want thoseerror messages to be located? How can utilizing animation in an interface affect the user experience? Explain how you could make an infographic accessiblefor screen reader users. Why is color alone insufficient to draw attention to actionable elements, or to convey state?
What are someof the inclusiveUX problems that need to be solved when content (static or actionable) is revealed on :hover, and how would you proposesolving for them? https://www.youtube.com/watch?v=pSOMZjm_lco https://www.youtube.com/watch?v=sJfwwEjmEfc What is ARIA? WAI-ARIA is the Accessible Rich Internet Applications specification from the Web Accessibility Initiative at the W3C. ARIA provides a means to make web applications and widgets more accessible to a diverse range of users, including those who use assistive technologies such as screen readers or magnifiers. ARIA provides additional semantics to describe the role, state, and functionality of many familiar user interface controls, such as menus, sliders, trees, and dialogs. It also provides additional structural information, helping authors identify landmarks, regions, and grids on their pages. ARIA enables dynamic, JavaScript-driven applications and widgets to interoperate with a variety of desktop-based assistive technologies. For more information about how to create accessible widgets with ARIA, see the Overview of accessible web applications and widgets. Where is ARIA Supported? ARIA is a relatively new specification, but support for it is growing. A wide variety of commonly-used browsers, assistive technologies, JavaScript toolkits, and applications now support ARIA. However, many users may still be using older versions of these technologies. You may want to consider implementing ARIA using progressive enhancement techniquessuch as adding ARIA using JavaScript, not directly to your markupin order to more gracefully support older browsers and assistive technologies.

More Related Content

Aria interview questions

  • 1. ARIA Interview Questions: Who benefits from accessibility? How would you define inclusive and/or universaldesign? o Can you providean example? (does not need to be web related) How has your approach to accessibility changed over time? Name some ways responsive/mobilefirstdesign can affect accessibility. What are someuser experience (UX) concerns to be awareof when using iconography in user interfaces (UI)? What assistivetechnologies (ATs) are you familiar with (desktop + mobile)? o What do you feel is your skilllevel with these AT(s)? Describethe purposeof heading and header elements, and how they are usefulin websites and web applications. What are skip links? o How can users benefit fromthem? o What are someof their limitations? What are someof the tools available to test the accessibility of a website or web application? How can using plain languagebenefit the accessibility of a project? Describeappropriateinstances to usea link, vs a generic button, vs a submit button. Describeways to indicate an element or components state that arent entirely reliant on visuals. How can carousels be problematic for users with disabilities? What are somedesign considerations for supporting text resize/zoomon web? Mobile apps? In whatways can the CSS display property affectthe accessibility of a document? What is the difference between legend and label elements? What is the purposeof the alt attribute for images? o Can you describe the effect of an empty alt, or the lack of the attribute, on an image? o In whatinstances might an empty alt or no alt be appropriate? o How might alternative text for an image vary, depending on the context the image is used in?
  • 2. o Since svgs dontaccept the alt attribute, how can one provide alternative text for these graphics? What methods would you use to find an elements accessible name? What is the accessibility tree? Why are rems or ems preferableto pixels for setting type size? Why is it important to allow the viewportto scale? How is the title attribute exposed to assistivetechnologies? o What kind of elements can title attributes be used on? o What sortof information is appropriatefor usewith the title attribute? Describea scenario where you might need to use aria-describedby. What are landmark roles and how can they be useful? For each element, when might you use a toggle button, a switch control, or a checkbox? Describemethods to hide content: o Fromall users. o Fromonly screen reader users. o Fromsighted users, butnot screen reader users. o And why you might do so. Is it possibleto overuseARIA in a website? Explain why or why not. Aside fromscreen readers, What other assistivetechnologies can be affected by useof ARIA? How? What is the difference between hidden, aria-hidden="true" and role="presentation" or role="none"? Describeinstances where you might need to use aria-live. o What values (such as assertiveor polite) might you give the attribute in different situations? How would you mark-up an icon font or SVG that was for decorative purposes? How is CSS pseudo content treated by screen readers?
  • 3. Describethe steps you take in reviewing or auditing a website or application for accessibility? Describean instance wherean automated test would not flag a blatant accessibility error? When should you use or recommend ARIA roles or attributes to solvean accessibility issue? Describeyour process for figuring out if an accessibility bug is due to a developer, browser, or assistivetechnology error? Describeyour thoughts on how a single page web app should handle focus when a new screen loads. Name an ARIA attribute that requires either a child/parent relationship or a pairing role. What is your understanding of accessiblename computation and how it affects modifying the way screen readers announce certain content? What are someissues with modifying normal scrolling behavior? For example: infinite scrolling or scrolljacking. Design Talk about the pros and cons of flat and skeuomorphic design trends in regards to accessibility. Explain the importance of color contrastin designing for inclusion. Besides :hover, name other states an actionable element (links, buttons, formcontrols, etc.) could havestyles for, and why providing them is important? When might it be appropriateto removethe visualoutline froma focused element? If a formor formfield were to return an error message, wheremight you want thoseerror messages to be located? How can utilizing animation in an interface affect the user experience? Explain how you could make an infographic accessiblefor screen reader users. Why is color alone insufficient to draw attention to actionable elements, or to convey state?
  • 4. What are someof the inclusiveUX problems that need to be solved when content (static or actionable) is revealed on :hover, and how would you proposesolving for them? https://www.youtube.com/watch?v=pSOMZjm_lco https://www.youtube.com/watch?v=sJfwwEjmEfc What is ARIA? WAI-ARIA is the Accessible Rich Internet Applications specification from the Web Accessibility Initiative at the W3C. ARIA provides a means to make web applications and widgets more accessible to a diverse range of users, including those who use assistive technologies such as screen readers or magnifiers. ARIA provides additional semantics to describe the role, state, and functionality of many familiar user interface controls, such as menus, sliders, trees, and dialogs. It also provides additional structural information, helping authors identify landmarks, regions, and grids on their pages. ARIA enables dynamic, JavaScript-driven applications and widgets to interoperate with a variety of desktop-based assistive technologies. For more information about how to create accessible widgets with ARIA, see the Overview of accessible web applications and widgets. Where is ARIA Supported? ARIA is a relatively new specification, but support for it is growing. A wide variety of commonly-used browsers, assistive technologies, JavaScript toolkits, and applications now support ARIA. However, many users may still be using older versions of these technologies. You may want to consider implementing ARIA using progressive enhancement techniquessuch as adding ARIA using JavaScript, not directly to your markupin order to more gracefully support older browsers and assistive technologies.