Techniques harvest by technology
General
- What is a good alt. For functional non-text content
- simple example is a calculator (1.1
L1 SC1)
- What captions are and audio description are and how
to provide (1.1
L1 SC1)
- Need to provide information about caption formats
that can be used - can link to other sites with that info (1.1
L1 SC1)
- Include discussion of open captioned format
alongside non-captioned (1.1
L1 SC1)
- Describe audio descriptions and how to create them (1.2
L1 SC2)
- Techniques for switching audio tracks (1.2
L1 SC2)
- ADI guidelines for AD - http://adinternational.org/adiguidelines.HTML
(1.2
L1 SC2)
- Time shifting (1.2
L2 SC1)
- Streaming captions: http://www.captioncolorado.com/products/internet.HTML
(1.2
L2 SC1)
- Captions being provided in a separate window (1.2
L2 SC1)
- Could also talk about open captions (1.2
L2 SC1)
- Providing sign language video e.g., vcom 3d http://www.vcom3d.com/
(1.2 L3
SC1)
- Get rnid to provide techniques (1.2 L3
SC1)
- Techniques for where to position (1.2 L3
SC1)
- Creating Extended Audio Descriptions in QuickTime http://ncam.wgbh.org/richmedia/tutorials/qtxad.HTML
(1.2
L3 SC2)
- AD tutorials: http://ncam.wgbh.org/richmedia/strategies/XAD.php
(1.2
L3 SC2)
- John Slatin's performance where the audio
description was scripted but done "live" (1.2 L3
SC3)
- Radio describes - that's why lots of people listen
to the radio and watch at the same time (1.2 L3
SC3)
- Relationship between caption/audio description and
multimedia (1.3
L1 SC1)
- Asterisk near required field instead of just making
it red (1.3
L1 SC2)
- Color for headings (1.3
L1 SC2)
- Encoding color so that it can be programmatically
determined: have to specify it a certain way so that ats can pick it up (1.3
L1 SC2)
- Indicating correct and incorrect (1.3
L1 SC2)
- Choosing technologies whose players expose text
attributes to AT (1.3
L2 SC1)
- Sequences between delivery units (1.3
L3 SC1)
- (only general) (1.4
L2 SC1)
- (general techniques) (1.4
L2 SC2)
- Provide links to tools to evaluate (1.4
L2 SC2)
- Strategy for measuring (1.4
L3 SC2)
- Keyboard access to controls used in mapping
programs (2.1
L3 SC1)
- Show time remaining (2.2
L1 SC1)
- Creating a time out with a way to turn it off (2.2
L1 SC1)
- Pausing multimedia (2.2 L2
SC2)
- Design content without requiring timing (2.2
L3 SC1)
- Address online testing (2.2
L3 SC1)
- Turning things off (2.2
L3 SC2)
- How to provide a good warning and using entry pages
(issues around controlling path users use to get to a page) (2.3
L1 SC1)
- Splash page that warns of issue before playing (2.3
L1 SC1)
- Use a checkbox on a page that presents a warning
before presenting content (2.3
L1 SC1)
- Just don't do it (2.3
L1 SC1)
- How to evaluate for problematic content (2.3
L1 SC1)
- Some way to determine whether or not they are
violating this (2.3 L3
SC1)
- Need to address what the problem space around these
criterion are (2.3 L3
SC1)
- Linking to related content (2.4
L2 SC1)
- How to assign effective metadata (2.4
L2 SC1)
- Allowing users to search as well as browse (2.4
L2 SC1)
- Links to most popular content (2.4
L2 SC1)
- Hide repeated content (2.4
L2 SC2)
- Writing a good title (2.4
L2 SC3)
- Titles being unique? (2.4
L2 SC3)
- Breadcrumb navigation (2.4
L3 SC2)
- Using icons and color to differentiate sections of
a site (2.4
L3 SC2)
- Negative technique around breaking the back button? (2.4
L3 SC2)
- Using different colors on visited vs. Unvisited
links (2.4
L3 SC2)
- Validation of credit card formats (2.5
L2 SC1)
- Writing understandable 401 or 404 pages (2.5
L2 SC1)
- Provide a guess when desired page is not found
"smart 404" (2.5
L2 SC1)
- Google "did you mean" example (2.5
L2 SC2)
- Provide a list of words that are similar (2.5
L2 SC2)
- Type 3 letters and provide a list of choices that
begin with those letters (2.5
L2 SC2)
- Use soundex codes (2.5
L2 SC2)
- Google suggest? Http://www.google.com/webhp?Complete=1&hl=en
(2.5
L2 SC2)
- Show similar search results/matches (2.5
L2 SC2)
- In page link from error message to field with the
error (2.5
L2 SC2)
- A featured link in amazon? (2.5
L2 SC2)
- Query enhancements (2.5
L2 SC2)
- Dividing processes into steps and allowing forward
and backward nav. (2.5
L2 SC3)
- Return a new form with only the incorrect fields
available (2.5
L2 SC3)
- Programmatically provide supplemental information -
tooltips with additional info or help (2.5
L2 SC3)
- Confirmation window opens to show user action has
completed (2.5
L3 SC1)
- Provide spell checking (2.5
L3 SC1)
- Help bubbles (2.5
L3 SC1)
- Tooltips using title (2.5
L3 SC1)
- Do not use same words or letter combinations to
begin each item of the list (2.5
L3 SC1)
- Providing help link on every page (2.5
L3 SC1)
- (annoying) assistant in the corner of the page (2.5
L3 SC1)
- How to use templates - put language in just once in
the template. This could also be used in many other areas (3.1 L1
SC1)
- Provide definitions via bubble help (3.1 L3
SC1)
- Provide hyperlinks to relevant online dictionaries (3.1 L3
SC1)
- Internal linking (3.1 L3
SC2)
- Expanded form presented first time it is used and
acronym is presented in parends after - then use acronym in subsequent
references (3.1 L3
SC3)
- Provide search engine to look up (3.1 L3
SC3)
- How to mark up section titles (3.1 L3
SC4)
- How to write descriptive titles (3.1 L3
SC4)
- Recommendations on how to provide the alternatives (3.1 L3
SC5)
- Front load the document - make first paragraph the
summary (3.1 L3
SC5)
- Make sure spoken version of text content is not
started automatically in the background or only at the user's request (3.1 L3
SC5)
- General tech about introducing subitems to clarify
allowed (3.2
L2 SC1)
- Change of context - a change of user agent,
viewport, user interface controls, or focus; or complete change of
content. (3.2
L2 SC2)
- This is more about generating the page rather than
fixing later. Perhaps general technique "just do it..." (3.2
L2 SC4)
- Test - if a graphic is associated with different
uris on different pages, flag them and determine if differences make
sense. If not, make consistent. (3.2
L3 SC1)
- No automatic refreshes, at all. (3.2
L3 SC2)
- Navigating around page, shouldn't cause change of
context (e.g., pop-ups). However, this meant to mean "only by user
request." (3.2
L3 SC2)
- Changes of user agent (3.2
L3 SC2)
- Change in user interface control? (3.2
L3 SC2)
- Links to alternatives (concern about these and
cyberghetto) (4.2
L1 SC1)
- Keyboard handling (4.2
L1 SC2)
- Not trapping keyboard (4.2
L1 SC2)
- "hit x to return to previous page"
covered by "must be able to use w/keyboard" (4.2
L1 SC2)
- Getting trapped in a plug-in (4.2
L1 SC2)
- Can never use contenteditable? Should document
workarounds/games/kludges related to (4.2
L1 SC2)
- There are techniques but can't validate right now
and don't have spec *yet* (4.2
L1 SC3)
- However, if use elements semantically correctly would
satisfy to best of ability. Also, in some techs (flash) don't' you have
to do for info to get passed through? (4.2
L1 SC3)
- Concern that people creating UI elements with a and
div and is that not using the elements semantically correctly (4.2
L1 SC3)
- Issue - is it possible to meet the strict
interpretation of this in HTML? If not, what is the intent? Can we meet
the intent with other wording? (4.2
L1 SC3)
- Point to external documentation that explains/shows (4.2
L1 SC6)
- Redundant with using accessibility conventions? No
- if use accessibility features, get for free. If not, need to do the
things in L1 SC6 (4.2
L1 SC6)
- People interpret this to mean that they have to use
all accessibility features (e.g., accesskey, tabindex) that not
necessarily the case (4.2
L2 SC1)
- Document the user agent issue where accessibility
features are not supported or supported inconsistently (4.2
L2 SC1)
HTML
- Link to a sequence of pages that provide function
(for some simple function): nightmare where page has to reload over and
over (1.1
L1 SC1)
- Text labels above and below the sensory content (1.1 L1
SC3)
- Consider no-script element with no content (1.1 L1
SC4)
- Link to stable site that provides description of
different options for real time captioning (1.2 L3
SC1)
- Emphasis element and coloring rather than just
using span with color (1.3
L1 SC2)
- (Similar to L1) (1.3
L2 SC2)
- Tabindex? May be covered by 2.4 (1.3
L3 SC1)
- bgsound, autoplay (1.4
L2 SC3)
- Using foreground and background colors (1.4
L3 SC1)
- onclick as mechanism to get focus (2.1
L1 SC1)
- tabindex, though user agent issues (2.1
L1 SC1)
- Anchors on image buttons (2.1
L1 SC1)
- Redundant links for server-side image maps (2.1
L3 SC1)
- Use of <map> to allow keyboard navigation (2.1
L3 SC1)
- Meta-refresh technique (2.2
L3 SC2)
- Foreground/background issues (2.3 L3
SC1)
- <link> and <a> (2.4
L1 SC1)
- Header elements (2.4
L1 SC1)
- Lists and groups of links (2.4
L1 SC1)
- onclick event handlers that take you to another page (2.4
L1 SC1)
- Autosubmit combo boxes (2.4
L1 SC1)
- Table of contents (2.4
L2 SC1)
- Revise HTML 9.7 to be more general? (currently
applies only to link groups) (2.4
L2 SC2)
- Ideally, using <div> would help (2.4
L2 SC2)
- Headers (2.4
L2 SC2)
- Tables (2.4
L2 SC2)
- Use spacer gif in link text so that it is not
visible where alt for spacer gif gives additional clarification (2.4
L2 SC4)
- For image maps, area element should exist in source
code in reasonable order (2.4
L3 SC1)
- HTML forms, if multiple submit buttons, be sure the
first one is the one you want to be default (may fit better under 2.1) (2.4
L3 SC1)
- Use of <link> element (2.4
L3 SC2)
- Text directionality (3.1 L1
SC1)
- Use of meta tag with content-language (unsure if
supported) (3.1 L1
SC1)
- What to do if specify more than one language in
header? (3.1
L2 SC1)
- <link rel="glossary"> (3.1 L3
SC1)
- Definition lists (3.1 L3
SC2)
- Need an alternative to "target" since not
allowed in strict HTML. Rel is external then programmatically open new
window. (3.2
L1 SC1)
- Discuss onfocus event handler and what not to do
when activated (3.2
L2 SC2)
- "On leaving a data field" (3.2
L3 SC2)
- Use links to cause page to refresh instead of
automatic refresh (3.2
L3 SC2)
- noframes, noscript (4.2
L1 SC1)
- Fallback mechanism for applets (if applet not in
baseline) need alternative mechanism for functionality (4.2
L1 SC1)
- Label element for most controls, alt for image
input, value for most buttons, text for button element (4.2
L1 SC4)
- "Creating Invisible labels for form
elements" is mapped here. Should remap to L1SC4 (4.2
L2 SC1)
CSS
- Using images as list item bullets (removed?) (1.1 L1
SC4)
- Background images are being used freq now for
decorative images (1.1 L1
SC4)
- Use CSS for non-essential background audio (1.1 L1
SC4)
- Positioning, styling (1.3
L1 SC1)
- Not using CSS as the only way to indicate a
blockquote (1.3
L2 SC1)
- Don't put stuff out of sequence (1.3
L3 SC1)
- Affecting the layout, when that fails, the order
should still be relevant (1.3
L3 SC1)
- For background images and colors (1.4
L1 SC1)
- Layered divs (1.4
L1 SC1)
- Using foreground and background colors (1.4
L3 SC1)
- Switch between using animated vs. Static images (2.2 L2
SC1)
- Foreground/background issues (2.3 L3
SC1)
- Allow keyboard users to view skip links (2.4
L2 SC2)
- Negative technique around illogical HTML source
order corrected by CSS (2.4
L3 SC1)
- Make sure people notice the text summary by using
diff. Presentation style (3.1 L3
SC5)
- CSS inherit w/inherit property children will accept
computed value of parent (3.2
L1 SC1)
- CSS about indenting text. Not properly mapped. (3.2
L2 SC1)
Script
- Non-text elements generated by script must have
text alternatives (1.1
L1 SC1)
- Need to show how to properly add non-text elements
that will work with at (1.1
L1 SC1)
- Using script for hiding content (1.1
L1 SC1)
- Putting it in a fashion so if script is not
supported it just disappears for decorative content-- this becomes a
tech. That just explains that you don't have to do anything (for
scripting that is not essential to operation) (1.1 L1
SC4)
- Create elements when creating new content (1.3
L1 SC1)
- Style switcher (1.3
L1 SC2)
- Cautionary - don't just change the color unless
also setting some structural attribute (1.3
L1 SC2)
- Script to provide style switcher (1.3
L3 SC1)
- Hiding layered divs (1.4
L1 SC1)
- Button (1.4
L2 SC3)
- Scripted cookie to remember settings (1.4
L2 SC3)
- Scripted colour changes to create violations that
weren't there before (1.4
L3 SC1)
- Moving text must have sufficient contrast with all
the places it can move to (1.4
L3 SC1)
- Creating a way to extend or modify time (2.2
L1 SC1)
- Implement blinking via script w/ a way to turn it
off (2.2 L2
SC1)
- Make text shake, there should be a script technique
to make it stop shaking (2.2 L2
SC2)
- JavaScript alerts? Issues around allowing users to
turn off alerts - might be a technique to allow people to prevent alerts (2.2
L3 SC2)
- Checking to find out if timeout is about to occur
and allowing users to submit before timeout occurs (2.2
L3 SC3)
- Can check preferences before serving problem
content (2.3
L1 SC1)
- Reference DHTML roadmap (2.4
L1 SC1)
- JavaScript url (sometimes navigational feature,
sometimes not) -- if you're using this as a navigational feature, don't (2.4
L1 SC1)
- From a list apart - use link element to create
drop-down menus (2.4
L2 SC1)
- Focus order for JavaScript menus (2.4
L3 SC1)
- Client side validation and scripting alert (2.5
L2 SC1)
- Client side validation and add error text via the
DOM (2.5
L2 SC1)
- Alert/pup-up with "Are you sure?" and ok,
cancel (2.5
L2 SC3)
- Way to highlight important words in the content via
button press and scripting/CSS (3.1 L3
SC2)
- Style sheet switcher or script tech. To switch
between diff. Version of a doc. (3.1 L3
SC5)
- Using "a" is one way to satisfy this.
Have technique for using? [or just refer to HTML spec] (3.2
L1 SC1)
- Does this address issue w/tabbing to menu item and
menu item opens automatically (on tab into)? (3.2
L2 SC2)
- On forms submit, have to use submit so that doesn't
rely on focus to cause submission (3.2
L2 SC2)
- Using onchange on select (in an accessible way)
somewhat controversial (but will log and explore) (3.2
L2 SC3)
- Question about: technique to address issue that
automatically advances you to next field after enter x # of characters?
When hit back to fix an entry, now in different field. (3.2
L2 SC3)
- Keyboard event handlers. How to return t/f if
handle or if OS handles. (4.2
L1 SC2)
- DHTML roadmap techniques (4.2
L1 SC5)
- Document.write (4.2
L1 SC6)
- All uses of JavaScript on a site (if script not in
baseline) are accessible and also work with out. (4.2
L3 SC1)
Other
- Link to server side implementation (1.1
L1 SC1)
- (Regarding accessing captions) store user settings
in a cookie (1.1
L1 SC1)
- Provide a script button to access the captions (1.1
L1 SC1)
- Link to flash techniques (1.1
L1 SC1)
- Client side forms validation with server side back
up (1.1 L1
SC3)
- Meta refresh for web cams - traffic cams for ex (1.1
L1 SC5)
- Techniques on picture in picture display SMIL
techniques for sizing and position in window or present in separate
window (1.2 L3
SC1)
- Same as audio descriptions, SMIL 2 will have a way
to pause video (1.2
L3 SC2)
- Cookie to remember settings (1.4
L2 SC3)
- Server-side tech to remember settings related to
timeouts (2.2
L1 SC1)
- Cover animated gifs (2.2 L2
SC1)
- Ticker-tape scrolling (various technologies) (2.2 L2
SC2)
- Server-side techniques around keeping data while
awaiting re-authentication (2.2
L3 SC3)
- Store intermediate results on multi-part surveys on
the server (2.2
L3 SC3)
- Use robots.txt to exclude violating content from
search engines (2.3
L1 SC1)
- Server-side tech about using search engines (2.4
L2 SC1)
- Server side tech that allows users to log back in,
see past transactions and cancel (2.5
L2 SC3)
- Server-side includes (3.2
L2 SC1)
- Templates (3.2
L2 SC1)
- CMS to help (3.2
L2 SC1)
- Content negotiation (4.2
L1 SC1)
- User settings, store preferences (4.2
L1 SC1)
- Style switcher (4.2
L1 SC1)
- Java, Flash techniques (4.2
L1 SC5)
- Primary concern now about programmatic objects.
Mapping to UAAG 1.0 that all things are covered. Eventually XHTML.
Perhaps confusing now for HTML developers, but need to document in guide
asap (4.2
L1 SC5)
- W/java if using classes that include accessibility
then get for free, but if not then need to ensure that do these things (4.2
L1 SC6)
- Tech is - follow techs for that tech (4.2
L3 SC1)