RE: [wbs] response to 'Curriculum "Developing Accessible Content" -- Monkey Review'

Thanks Kevin,

See replies below. 


> > > Comments:
> > > There are a number of points that suggest WAI-ARIA i native elements
> > > can't be used. I wonder if there might be a need to include
> > > something of learning
> > outcome around understanding why this can be problematic and what is
> > involved in taking this approach.
> >
> > I have included a new learning outcome for module
> >
> > * identify the benefits of using HTML native elements to the extent
> > possible for broader compatibility with assistive technologies and
> > adaptive strategies
> >
> > That focuses on the general preference of HTML over ARIA. Instead of
> > saying Aria can be dangerous, we say HTML native markup is preferred.
> > Are you comfortable with this wording?
> Principle is good but I think the wording is slightly off. Maybe:
> 
> * outline the benefits of using HTML native elements for compatibility with assistive technologies and adaptive strategies
> 
Changed.
 
> > > Additional Comments:
> > > I wonder if there is a slight elephant in the room: many front end
> > > developers don't code in HTML but use a framework such as React.
> > > This means they aren't building pages in the ways outlined in these
> > > courses and may
> > consider it not relevant to them. Do we need to acknowledge this in some way?
> >
> > I am not sure if I understand correctly. Is it the word "Code" that is
> > around in many learning outcomes that may be problematic? Would it
> > help if we acknowledge that these coding techniques that we provide
> > can (and should) also be implemented at a framework level for the framework to produce accessible code?
> 
> I have spoken with front end developers who don't know how to code in HTML. They write everything in React were quite surprised when I
> pointed out that that was translated into HTML.
> 
> I might be overly worried about this but just something that has been problematic when speaking with a number of developers in the past.

It is true that this curriculum does not show you how you can tweak REACT or any of those frameworks to make their output accessible. So if a developer doesn't know how to use HTML, then probably the best answer we can give to them is: knowledge of HTML is advised as a prerequisite for courses based on this curriculum. We say that in the overview page, section "prerequisites", last paragraph.
For those who do know how to use HTML but still are using these types of frameworks, we could add something on the front-page along the lines of: "Guidance to implement these HTML, CSS, and JavaScript techniques in your framework of choice is out-of-scope for this curriculum".

Would you be comfortable marking this particular use case as out-of-scope?

Best.

--

Daniel Montalvo

Accessibility Education and Training Specialist
W3C/WAI

Received on Tuesday, 20 October 2020 13:59:53 UTC