I've been working on making the default MODX theme more responsive and have some questions about if this work does or does not relate to the accessibility campaign.
The MODX Accessibility page claims it will make a theme that is a
first-class citizen of the accessible software world
Is responsive design and support for mobile viewports part of what you consider makes first-class accessible software? Or does a11y just mean ARIA roles, contrast, and keyboard navigation enough to claim first-class accessibility support?
Just trying to get a sense of what accessibility actually means to the
team of experienced professionals in both Accessibility and advanced Manager development
because the way accessibility seems to be defined here deviates from the WCAG and industry standards. Do we consider something that is not responsive, and thus cannot be used on smaller viewports, accessible?
When pull requests like https://github.com/modxcms/revolution/pull/12776 are submitted back to the default MODX theme by community contributors will they have any chance of being merged into the a11y theme as they cannot directly target it?
Hi JP … it's very much in line with what's going on with a11y. Much, if not all, of the work done on the a11y theme will hopefully become part of the core/default theme.
I've been working on making the default MODX theme more responsive and have some questions about if this work does or does not relate to the accessibility campaign.
The MODX a11y theme is far from mobile friendly. The default theme is making significant progress though: https://github.com/modxcms/revolution/pull/12776
The MODX Accessibility page claims it will make a theme that is a
Is responsive design and support for mobile viewports part of what you consider makes first-class accessible software? Or does a11y just mean ARIA roles, contrast, and keyboard navigation enough to claim first-class accessibility support?
Just trying to get a sense of what accessibility actually means to the
because the way accessibility seems to be defined here deviates from the WCAG and industry standards. Do we consider something that is not responsive, and thus cannot be used on smaller viewports, accessible?
When pull requests like https://github.com/modxcms/revolution/pull/12776 are submitted back to the default MODX theme by community contributors will they have any chance of being merged into the a11y theme as they cannot directly target it?