Re: Proposal for Requirements - Introductory paragraph on Scope

+1

Cheers,
David MacDonald



*Can**Adapt* *Solutions Inc.*

Tel:  613-806-9005

LinkedIn
<http://www.linkedin.com/in/davidmacdonald100>

twitter.com/davidmacd

GitHub <https://github.com/DavidMacDonald>

www.Can-Adapt.com <http://www.can-adapt.com/>



*  Adapting the web to all users*
*            Including those with disabilities*

If you are not the intended recipient, please review our privacy policy
<http://www.davidmacd.com/disclaimer.html>


On Fri, Apr 26, 2019 at 2:32 PM Léonie Watson <lw@tetralogical.com> wrote:

> +1
>
>
> On 26/04/2019 17:58, Jeanne Spellman wrote:
> > Github and I are not getting along today, and I fear that this proposal
> > won't be available in Github in time for the meeting.
> >
> > We were asked to add a paragraph to the Introduction clarifying the
> > Scope of Silver.  Here's what I propose:
> >
> >
> >       1.1 Scope
> >
> > Silver will have a broader scope than WCAG 2.0 and 2.1. The Web Content
> > Accessibility Guidelines (WCAG) are scoped to Web and to Content. Silver
> > is being deliberately designed to be able to include:
> >
> >   * *Disability Needs*: An improved measurement and conformance
> >     structure that includes guidance for a broad range of disabilities.
> >     This includes particular attention to the needs of low vision and
> >     cognitive accessibility, whose needs don't tend to fit the
> >     true/false statement success criteria of WCAG 2.x.
> >   * *Emerging Technologies*: Flexibility to include emerging
> >     technologies, such as Virtual Reality (VR) and Voice Assistants
> >   * *Support for the Technologies that Impact Accessibility*: Advice for
> >     all levels of the accessibility technology stack who wish to support
> >     the Silver core Guidelines including:
> >       o *web content*, which will be migrated from WCAG 2.x
> >       o *authoring tools*, such as content management systems
> >       o *user agents*, such as browsers, media players
> >       o *software and web applications*, including mobile apps
> >       o *assistive technologies*, such as screen readers, screen
> >         magnifiers, and assistants for memory, organizational, or
> >         simplification
> >       o *operating systems* and other platforms who may want advice for
> >         features to better support people with disabilities
> >
> > The current project design does not intend to write separate
> > specifications or normative requirements for the technology stack. The
> > goal is to provide information that technology venders can choose to use
> > to improve the accessibility of their products.
> >
>
> --
> @TetraLogical TetraLogical.com
>
>