starshot-prototype
starshot-prototype copied to clipboard
phenaproxima
Make Our Starshot Accessible
What do we need to do to make Starshot accessible? If this is a "completely new Drupal" then we need to make sure that we are building in accessibility best practices from the start. Some thoughts:
- What are the known accessibility problems in the components which will make up Starshot?
- How do we go beyond the automated testing already in Core to ensure that we are catching new issues earlier in the process?
- What can we do now to make sure that additional flexibility does not inadvertently exclude people?
- As a leading open source CMS, we've made commitments to keep up with accessibility best practices as defined by the W3C https://www.drupal.org/about/features/accessibility - which impacts both the user and author facing pieces?
Starshot will take a big investment from our community, but we have to see it doesn't exclude people as part of this process.
a heavy plus one to mikes point, but i would extend the question and ask to what degree core gates should apply to modules added to Starshot? I am looking at it from an ux perspective, which is overlapping with a11y anyway.
#142 is aiming to add some accessibility stuff (though obviously it's an ongoing thing, and a core design principle).
https://github.com/phenaproxima/starshot-prototype/pull/147 has been created to enable high contrast mode in the gin admin theme to help improve accessibility.
https://github.com/phenaproxima/starshot-prototype/pull/148 has been created to install the core inline form errors module to help improve the accessibility of Drupals forms.
FYI: https://github.com/phenaproxima/starshot-prototype/pull/142 now only includes the addition of the editoria11y module.