W3C home > Mailing lists > Public > public-silver@w3.org > April 2019

Re: Proposal for Requirements - Introductory paragraph on Scope

From: Léonie Watson <lw@tetralogical.com>
Date: Fri, 26 Apr 2019 19:32:44 +0100
To: Jeanne Spellman <jspellman@spellmanconsulting.com>, Silver Task Force <public-silver@w3.org>
Message-ID: <162dc6ff-e82f-79c3-22bd-d04c6e8a8b17@tetralogical.com>

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
Received on Friday, 26 April 2019 18:33:12 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:31:45 UTC