Skip to main content

Accessibility Questions

Sources​

General​

What are some overall recommendations to increase your website's accessibility:​

  • Website-specifics:

    • pages are consistent — navigation, header, footer, and main content are always in the same places.
    • tools are well-designed and easy to use.
    • multi-stage processes are broken down into logical steps, with regular reminders of how far through the process you are, and how long you've got left to complete the process, if appropriate.
    • workflows are logical, simple, and require as few interactions as possible to complete. For example, registering and signing in to a website is often unneccessarily complex.
    • pages are not overly long or dense in terms of the amount of information presented at once.
    • the language used in your pages is as plain and easy to follow as possible, and not full of unneccessary jargon and slang.
    • important points and content are highlighted in some way. user errors are clearly highlighted, with help messages to suggest solutions.

  • Consider accessibility from the start of your project instead of trying to retrofit your website

  • Publish an accessibility statement on your site that details what your policy is toward accessibility

  • https://developer.mozilla.org/en-US/docs/Learn/Accessibility/What_is_accessibility

[↑] Back to top

What is WCAG and where can you learn about some of the accessibility requirements?​

  • WCAG stands for Web Content Accessibility Guidelines.

  • There are two major sources:

  • WCAG appears to have four major principles: Perceivable, Operable, Understandable, Robust.

  • Perceivable

    • Provide text alternatives for non-text content.
    • Provide captions and other alternatives for multimedia.
    • Create content that can be presented in different ways, including by assistive technologies, without losing meaning.
    • Make it easier for users to see and hear content.

  • Operable

    • Make all functionality available from a keyboard.
    • Give users enough time to read and use content.
    • Do not use content that causes seizures or physical reactions.
    • Help users navigate and find content.
    • Make it easier to use inputs other than keyboard.

  • Understandable

    • Make text readable and understandable.
    • Make content appear and operate in predictable ways.
    • Help users avoid and correct mistakes.

  • Robust

    • Maximize compatibility with current and future user tools.

  • Sources:

[↑] Back to top

Who benefits from accessibility?​

[↑] Back to top

[↑] Back to top

How has your approach to accessibility changed over time?​

[↑] Back to top

Name some ways responsive/mobile first design can affect accessibility.​

[↑] Back to top

What are some user experience (UX) concerns to be aware of when using iconography in user interfaces (UI)?​

[↑] Back to top

What assistive technologies (ATs) are you familiar with (desktop + mobile)?​

  • What do you feel is your skill level with these AT(s)?

[↑] Back to top

Describe the purpose of heading and header elements, and how they are useful in websites and web applications.​

[↑] Back to top

  • How can users benefit from them?

  • What are some of their limitations?

[↑] Back to top

What are some of the tools available to test the accessibility of a website or web application?​

[↑] Back to top

How can using plain language benefit the accessibility of a project?​

[↑] Back to top

[↑] Back to top

Describe ways to indicate an element or component's state that aren't entirely reliant on visuals.​

[↑] Back to top

How can carousels be problematic for users with disabilities?​

[↑] Back to top

What are some design considerations for supporting text resize/zoom on web? Mobile apps?​

[↑] Back to top

In what ways can the CSS display property affect the accessibility of a document?​

[↑] Back to top

What is the difference between legend and label elements?​

[↑] Back to top

What is the purpose of the alt attribute for images?​

  • Can you describe the effect of an empty alt, or the lack of the attribute, on an image?

  • In what instances might an empty alt or no alt be appropriate?

  • How might alternative text for an image vary, depending on the context the image is used in?

  • Since svgs don't accept the alt attribute, how can one provide alternative text for these graphics?

Technical​

[↑] Back to top

What methods would you use to find an element's accessible name?​

[↑] Back to top

What is the accessibility tree?​

[↑] Back to top

Why are rems or ems preferable to pixels for setting type size?​

[↑] Back to top

Why is it important to allow the viewport to scale?​

[↑] Back to top

How is the title attribute exposed to assistive technologies?​

  • What kind of elements can title attributes be used on?

  • What sort of information is appropriate for use with the title attribute?

[↑] Back to top

Describe a scenario where you might need to use aria-describedby.​

[↑] Back to top

What are landmark roles and how can they be useful?​

[↑] Back to top

For each element, when might you use a toggle button, a switch control, or a checkbox?​

[↑] Back to top

Describe methods to hide content​

  • From all users.
  • From only screen reader users.
  • From sighted users, but not screen reader users.
  • And why you might do so.

[↑] Back to top

Is it possible to overuse ARIA in a website? Explain why or why not.​

[↑] Back to top

Aside from screen readers, What other assistive technologies can be affected by use of ARIA? How?​

[↑] Back to top

What is the difference between hidden, aria-hidden="true" and role="presentation" or role="none"?​

[↑] Back to top

Describe instances where you might need to use aria-live.​

  • What values (such as assertive or polite) might you give the attribute in different situations?

[↑] Back to top

How would you mark-up an icon font or SVG that was for decorative purposes?​

[↑] Back to top

How is CSS pseudo content treated by screen readers?​

[↑] Back to top

Describe the steps you take in reviewing or auditing a website or application for accessibility?​

[↑] Back to top

Describe an instance where an automated test would not flag a blatant accessibility error?​

[↑] Back to top

When should you use or recommend ARIA roles or attributes to solve an accessibility issue?​

[↑] Back to top

Describe your process for figuring out if an accessibility bug is due to a developer, browser, or assistive technology error?​

[↑] Back to top

Describe your thoughts on how a single page web app should handle focus when a new screen loads.​

[↑] Back to top

Name an ARIA attribute that requires either a child/parent relationship or a pairing role.​

[↑] Back to top

What is your understanding of "accessible name computation" and how it affects modifying the way screen readers announce certain content?​

[↑] Back to top

What are some issues with modifying normal scrolling behavior? For example: infinite scrolling or scrolljacking.​

Design​

[↑] Back to top

Explain the importance of color contrast in designing for inclusion.​

[↑] Back to top

[↑] Back to top

When might it be appropriate to remove the visual outline from a focused element?​

[↑] Back to top

If a form or form field were to return an error message, where might you want those error messages to be located?​

[↑] Back to top

How can utilizing animation in an interface affect the user experience?​

[↑] Back to top

Explain how you could make an infographic accessible for screen reader users.​

[↑] Back to top

Why is color alone insufficient to draw attention to actionable elements, or to convey state?​

[↑] Back to top

What are some of the inclusive UX problems that need to be solved when content (static or actionable) is revealed on :hover, and how would you propose solving for them?​

[↑] Back to top