<![CDATA[ MODX Accessibility Forces - My Forums]]> https://forums.modx.com/thread/?thread=83643 <![CDATA[Re: MODX Accessibility Forces]]> https://forums.modx.com/thread/83643/modx-accessibility-forces#dis-post-540220 Quote from: Bruno17 at Apr 04, 2013, 04:33 AM
Since most of us would like to see extjs in the modx3-manager again wink
This may be interesting:
http://docs.sencha.com/ext-js/4-0/#!/video/17840717

I think we need to stop framing the conversation around there being a single JavaScript framework in the MODX 3 Manager. IMO the MODX way would be to ship the core product with web standards that can be progressively enhanced however developers like. AngularJS, React, Ember, every other JavaScript framework or library, all those things have one thing in common: they are compatible with VanillaJS.

So, if we can can go about architecting the front end, and the API, in a more standard way I think we can see a Manager that uses any number of frameworks with direct on the user experience. For example, imagine being able to switch from AngularJS to React without affecting the display and UX of components at all. Imagine being able to use the two together on the same page.]]> dinocorn Apr 07, 2016, 06:03 AM https://forums.modx.com/thread/83643/modx-accessibility-forces#dis-post-540220 <![CDATA[Re: MODX Accessibility Forces]]> https://forums.modx.com/thread/83643/modx-accessibility-forces#dis-post-462424
The point is: WAI-ARIA is not at all ready for use in web apps. Up to now, browsers and screenreaders did a good job in implementing WAI-ARIA landmarks and forms support – a very little part compared to what we would need for web apps built of custom controls. For the time being we should better rely on HTML than WAI-ARIA. HTML has all it takes for accessibility.

Susan made a good point when wanting an “unobtrusive” Manager. You certainly heard of the layer model in standards-conformant web dev:
- HTML is for content and structure
- CSS is for presentation
- Javascript is for behavior
This means of course to avoid script-generated content to the minimum. If we do it like this, accessibility problems will tend to zero – not to forget the design rules given in WCAG, of course.

I can’t wait to do in real smiley
]]> BrigitteB Apr 10, 2013, 02:05 PM https://forums.modx.com/thread/83643/modx-accessibility-forces#dis-post-462424 <![CDATA[Re: MODX Accessibility Forces]]> https://forums.modx.com/thread/83643/modx-accessibility-forces#dis-post-461580 http://words.steveklabnik.com/emberjs-and-accessibility.

Ember JS is built on JQuery and Handlebars and should probably be considered for the MODX 3 Manager.]]> BobRay Apr 04, 2013, 12:09 AM https://forums.modx.com/thread/83643/modx-accessibility-forces#dis-post-461580 <![CDATA[Re: MODX Accessibility Forces]]> https://forums.modx.com/thread/83643/modx-accessibility-forces#dis-post-461576 sottwell Apr 03, 2013, 11:41 PM https://forums.modx.com/thread/83643/modx-accessibility-forces#dis-post-461576 <![CDATA[Re: MODX Accessibility Forces]]> https://forums.modx.com/thread/83643/modx-accessibility-forces#dis-post-461574
This may be interesting:
http://docs.sencha.com/ext-js/4-0/#!/video/17840717]]> Bruno17 Apr 03, 2013, 11:33 PM https://forums.modx.com/thread/83643/modx-accessibility-forces#dis-post-461574 <![CDATA[MODX Accessibility Forces]]> https://forums.modx.com/thread/83643/modx-accessibility-forces#dis-post-461530
It is still too early to figure out what has to be done in detail. The good news is that we can start from scratch, implementing accessibility during the design phase, then going forward step by step through development. Best conditions to achieve a good result.

For the time being we should join our forces.

Hello out there, are there any other accessibility people? Or people interested in accessibility? – I would be glad to hear from you. Please feel free to start any discussion or question related to MODX and accessibility.

See you
Brigitte]]> BrigitteB Apr 03, 2013, 03:50 PM https://forums.modx.com/thread/83643/modx-accessibility-forces#dis-post-461530