Accessibility
Classification of problem
For ease of task prioritization, we divide accessibility problems into proven and unproven problems.
Unproven A question or assertion regarding accessibility within ds without evidence of real impact.
Such issues are more difficult to address because they do not provide new evidence or relevant research.
Regarding special capacity issues related to theoretical implementation accessibility, the team will check the following:
Documented decisions taken in relation to ongoing implementation
Overlap with other issues and requests raised
Additional community resources related to accessibility issues
Proven Sharing new research, data and evidence to show that implementation in the design system can create barriers for people with disabilities.
User feedback and other evidence of real-world impact provides much more compelling evidence for the team, especially when prioritizing and determining urgency. If the solution to an accessibility problem involves a solution that results in a critical change, compelling evidence helps justify the change.
Many types of evidence can point to a proven accessibility problem, but here are some of the most common examples:
New research results
Usability testing results
New practices or standards
Feedback from users
Demonstration of unintended behavior of assistive technology
Accessibility audit results
Accessibility check tools
Google's Lighthouse extension allows you to audit your site for basic accessibility rules and also check the accessibility tree
WAVE browser plugin
Axe browser plugin
Screen readers and apps that voice content and interface from a device screen. (VoiceOver on iOS , TalkBack on Android, NVDA)
Built-in Storybook service tools
Linters and plug-ins stylelint-a11y, eslint-plugin-jsx-a11y, eslint-plugin-react-native-a11y and aatt.will help automate code validation, as well as integrate accessibility more easily.
When new evidence of a potential accessibility problem is received, the team will analyze and determine if it is a problem:
Has been previously reviewed or evaluated
Violates WCAG AA compliance
Is of high severity
Complexly planned tasks
Realistic tasks
Control color contrast/contrast mods
Increase color contrast to AA or AAA
Adding explanatory feedback icons to components
Prepare the interface for 200% scalability
Increase font size
Provide text alternatives for non-text content (alt)
Make clickable elements obvious
Add descriptive link text
Standardize attention focus patterns (F,Z patterns)
Add ARIA markup
Simplify and reduce the length of texts
Add subtitles or transcriptions
Develop uniform navigation patterns
Add voice navigation capability
Uniform behavior of similar interface elements
Add the ability to navigate using the keyboard