RE: WCAG A11Y DPUB techniques

Whether or not you want Flash to exist, it would be nice for publishers to know what to do with it. We have thousands of hours of Flash from when it was the best game it town. If the recommendation is convert it, make that known.

Tzviya Siegman
Digital Book Standards & Capabilities Lead
Wiley
201-748-6884
tsiegman@wiley.com 


-----Original Message-----
From: Deborah Kaplan [mailto:dkaplan@safaribooksonline.com] 
Sent: Wednesday, March 25, 2015 10:43 AM
To: George Kerscher
Cc: Charles LaPierre; public-dpub-accessibility@w3.org
Subject: RE: WCAG A11Y DPUB techniques

I actually don't think it is possible to give Flash keyboard-accessible controls and yet keep it from being a keyboard trap, even if you make it otherwise accessible. On the other hand, WCAG allows Flash; given that, is it permissible/reasonable for our group to disallow it?

On Wed, 25 Mar 2015, George Kerscher wrote:

> I am in agreement with Steve Jobs; Flash should not be allowed. I 
> understand that it is technically possible to make it accessible, and 
> I think I saw one at some point that I could use. However, my 
> experience is that it is mostly inaccessible.
>
> My $.02
>
> Best
> George
>
>
> From: Charles LaPierre [mailto:charlesl@benetech.org]
> Sent: Wednesday, March 25, 2015 8:14 AM
> To: George Kerscher
> Cc: public-dpub-accessibility@w3.org
> Subject: Re: WCAG A11Y DPUB techniques
>
> Hi George, we assigned Flash to Livio, who thought they were all 
> relevant but you think we shouldn’t bother with Flash for DPUB at all?  
> Don’t you think some publishers may want to publish some Flash content 
> in their web-based publication?
>
> _______________________________
>
> Charles LaPierre
> charlesl@benetech.org
>
>
>
> On Mar 25, 2015, at 6:52 AM, George Kerscher <kerscher@montana.com> wrote:
>
> Hi,
>
> I must have missed the call where flash was discussed. I would put 
> this in the same camp as silverlight; I would say it is not allowed.
>
> Best
> George
>
>
> From: Charles LaPierre [mailto:charlesl@benetech.org]
> Sent: Wednesday, March 25, 2015 7:36 AM
> To: public-dpub-accessibility@w3.org
> Subject: WCAG A11Y DPUB techniques
>
> Hello DPUB Accessibility TF,
>
> For the past few months we have gone through the WCAG Techniques 
> looking to see what was relevant to DPUB.  Here is a summary of what we found so far.
> We need to discuss the items that we feel are not required for DPUB 
> and those we still had questions about so we can determine if they are 
> relevant or not to DPUB.  Hopefully we can discuss these at our next 
> meeting.  I will send out a reminder and hopefully a new time slot for 
> this Friday if we can get the phone system switched over in time to host our call.
>
> Here are the WCAG techniques and what we feel are relevant to DPUB.
>
> WCAG A11Y DPUB ARIA Techniques
> All Relevant
>
>
> WCAG A11Y DPUB Flash Techniques
> All Relevant
>
>
> WCAG A11Y DPUB Plain Text Techniques
> All Relevant
>
> WCAG A11Y DPUB SMIL Techniques
> All Relevant
>
> WCAG A11Y DPUB Common Failures
> All Relevant
>
>
> A11Y DPUB Techniques (THIS IS NEW)
> Possibly Additions
>
> Page Numbers
>
> Drop Caps
>
> Notes (Footnotes, Asides, Author Notes, etc.)
>
> positional location of text to indicate different speakers,
>
> phonetic spellings of proper nouns (maybe indi work in w3c?)
>
> how does layout improve comprehension?
> *More work is needed here to flesh out missing WCAG techniques 
> relevant to DPUB.
>
>
> WCAG A11Y DPUB Silverlight Techniques
> All Not Relevant (Silverlight has begun End Of Life)
>
>
> WCAG A11Y DPUB General - Technique Development Assignments Not 
> Required
>
> G1: Adding a link at the top of each page that goes directly to the 
> main content area
>
> G9: Creating captions for live synchronized media
>
> G63: Providing a site map
>
> G71: Providing a help link on every Web page
>
> G157: Incorporating a live audio captioning service into a Web page
>
> G174: Providing a control with a sufficient contrast ratio that allows 
> users to switch to a presentation that uses sufficient contrast
>
> G175: Providing a multi color selection tool on the page for 
> foreground and background colors
>
> G178: Providing controls on the Web page that allow users to 
> incrementally change the size of all text on the page up to 200 
> percent
>
> G180: Providing the user with a means to set the time limit to 10 
> times the default time limit
>
> G181: Encoding user data as hidden or encrypted data in a 
> re-authorization page
>
> G185: Linking to all of the pages on the site from the home page
>
> G188: Providing a button on the page to increase line spaces and 
> paragraph spaces
>
> G189: Providing a control near the beginning of the Web page that 
> changes the link text
>
> G200: Opening new windows and tabs from a link only when necessary
>
> G201: Giving users advanced warning when opening a new window
>
> Not Sure
>
> G177: Providing suggested correction text
>
> G179: Ensuring that there is no loss of content or functionality when 
> the text resizes and text containers do not change their width
>
>
> G133: Providing a checkbox on the first page of a multipart form that 
> allows users to ask for longer session time limit or no session time 
> limit
>
> G139: Creating a mechanism that allows users to jump to errors
>
> G143: Providing a text alternative that describes the purpose of the 
> CAPTCHA
>
> G144: Ensuring that the Web Page contains another CAPTCHA serving the 
> same purpose using a different modality
>
> G155: Providing a checkbox in addition to a submit button
>
> G164: Providing a stated time within which an online request (or
> transaction) may be amended or canceled by the user after making the 
> request
>
>
> WCAG A11Y DPUB HTML Techniques
> Not Sure
>
> H35: Providing text alternatives on applet elements
>
> H84: Using a button with a select element to perform an action
>
> H85: Using OPTGROUP to group OPTION elements inside a SELECT
>
> H89: Using the title attribute to provide context-sensitive help
>
> H93: Ensuring that id attributes are unique on a Web page
>
>
> H86: Providing text alternatives for ASCII art, emoticons, and 
> leetspeak
>
> H91: Using HTML form controls and links
>
>
>
> WCAG A11Y DPUB CSS Techniques
> Not Relevant
>
> C9: Using CSS to include decorative images
>
> C28: Specifying the size of text containers using em units
>
> C29: Using a style switcher to provide a conforming alternate version
>
> Not Relevant but this is a powerful customization that is constantly 
> being used on the web.
>
>
> C15: Using CSS to change the presentation of a user interface 
> component when it receives focus
>
> Not Sure
>
> C7: Using CSS to hide a portion of the link text
>
> C12: Using percent for font sizes
>
> C22: Using CSS to control visual presentation of text
>
> C23: Specifying text and background colors of secondary content such 
> as banners, features and navigation in CSS while not specifying text 
> and background colors of the main content
>
> C26: Providing options within the content to switch to a layout that 
> does not require the user to scroll horizontally to read a line of 
> text
>
> C30: Using CSS to replace text with images of text and providing user 
> interface controls to switch
>
> C14: Using em units for font sizes
>
>
> WCAG A11Y DPUB PDF Techniques
> Not Relevant
>
> PDF7: Performing OCR on a scanned PDF document to provide actual text
>
>
> WCAG A11Y DPUB Server-Side Scripting Techniques Not Sure
>
> SVR1: Implementing automatic redirects on the server side instead of 
> on the client side
>
> SVR2: Using .htaccess to ensure that the only way to access 
> non-conforming content is from conforming content
>
> SVR3: Using HTTP referer to ensure that the only way to access 
> non-conforming content is from conforming content
>
> SVR4: Allowing users to provide preferences for the display of 
> conforming alternate versions
>
> SVR5: Specifying the default language in the HTTP header
>
>
> WCAG A11Y DPUB Client-side Scripting Techniques Not Relevant
>
> SCR24: Using progressive enhancement to open new windows on user 
> request
>
> SCR28: Using an expandable and collapsible menu to bypass block of 
> content
>
> SCR30: Using scripts to change the link text
>
> Not Sure
>
>
> SCR29: Adding keyboard-accessible actions to static HTML elements
>
>
> SCR1: Allowing the user to extend the default time limit
>
> SCR14: Using scripts to make nonessential alerts optional
>
> SCR18: Providing client-side validation and alert
>
> SCR21: Using functions of the Document Object Model (DOM) to add 
> content to a page
>
> SCR22: Using scripts to control blinking and stop it in five seconds 
> or less
>
> SCR31: Using script to change the background color or border of the 
> element with focus
>
> SCR32: Providing client-side validation and adding error text via the 
> DOM
>
> SCR33: Using script to scroll content, and providing a mechanism to 
> pause it
>
> SCR35: Making actions keyboard accessible by using the onclick event 
> of anchors and buttons
>
> SCR36: Providing a mechanism to allow users to display moving, 
> scrolling, or auto-updating text in a static window or area
>
> SCR37: Creating Custom Dialogs in a Device Independent Way
>
> SCR27: Reordering page sections using the Document Object Model
>
> Thanks.
>
> _______________________________
>
> Charles LaPierre
> <mailto:charlesl@benetech.org> charlesl@benetech.org
>
>

Received on Wednesday, 25 March 2015 15:25:16 UTC