Mozilla 1.0Mozilla OrganizationWindows 2000HTML 4.01Matt MayW3C+1-206-778-9065mcm@w3.org16 August 2002ACACCCCCCCCCCNRCCCCCPIonclick/ondblclick/onmouseover/onmouseout events failCCPIACNICCCCCNICPICNINICCNICCACACCCPIPICCNINRNRCouldn't discover how to disable IFRAMENRPINININRCCCCCNIPICCCNRNRNRNINININRCCCCCNINANANANANANANIAL: * No ALT repair strategies in place. * Reasons: The title attribute is almost never present when the alt isn't. In the rare cases where it is, it is of no help (typically it's just the filename, maybe with a file size). Also, in the overwhelming majority of cases, the filename is unintelligible. Developers interested in this problem can look at the GetAlternateText() method -- see the CVS history for suggestions. We consider this to be a very difficult problem. NINININININININININININRAL: * We have no repair strategy in 2.7 * We have no way to configure that alt="" still needs to be repaired * Needs to generate repair text for missing ALT attribute information for IMG element NINININIPIAL: * ALT for images * TITLE for tooltip PIPINRNRNRCAL: * Preferences, Appearance, Colors - "Use my chosen colors, ignoring the colors and background image specified" NRCCCPIAL: * Animated images can be made still with the Escape key * Animated images can be made still as a preference under Preferences, Privacy and Security, Images - "Animated Images should Loop" * Mozilla has no preference or command to toggle audio or video PIACAL: * The following line can be added to a user's prefs.js file to control blinking: user_pref("browser.blink_allowed",false); * Bug 89144 has been filed to expose this pref in the UI. * Mozilla doesn't support <marquee> by default. PIACACCCAL: Preferences, Advanced, Scripts and Windows - Enable Javascript For When toggled off, we don't notify the user when a page is loaded with scripts CNINININIACAL: * Our interface for image toggling needs redesign * Unfortunately, there are quite a few open bugs on image toggling ACACACCAL: * Can be changed through preferences, zooming or user style sheet. Zooming is really the best solution, because the document retains its look - all font sizes are increased the same percentage. * Zooming can be controlled via hotkeys Ctrl+plus and Ctrl+minus * The prefs are at Preferences, Appearances, Fonts * There is also a hidden pref line that can be added to prefs.js, if you just want to change the minimum font size for a certain font: user_pref("font.minimum-size.x-western", newFontSizeInPoints) * For other i18n charsets, change x-western to x-central-euro, x-cyrillic, x- unicode, x-user-def, x-baltic, el, tr, he, ar, th, ja, zh-CN or zh-TW CCCCCCCAL: Can be changed through preferences or user style sheet The prefs are at Preferences, Appearances, Fonts CCCCCAC * Can be changed through preferences or by editing the prefs.js file * The prefs are at Preferences, Appearances, Colors * To use any color offered in Windows, the prefs.js file must be edited by handACACACACACNICannot slow animations NININININANANANANANANANANANANANANANANANANANANANANANANANANANACAL: Under View Menu, Use Style Sheet -- allows one user style sheet to be applied at a time CCCCAL: Preferences, Advanced, Scripts and Windows - Allow Scripts To "Open Unrequested Windows" CCAL: Windows can be configured so that the window with the current focus is always on top. CACAL: * Preferences, Advanced, Scripts and Windows - Allow Scripts To "Open Unrequested Windows" * We do not have a strategy to 'alert the user and allow the user to open it on demand' * We do not have exposed prefs for all of our popup control options. * Here are all the "hidden prefs" lines that can be added to the user's prefs.js file, for controlling popup behavior: * Turn window.open off for particular sites: user_pref("capability.policy.popupsites.sites", "http:// www.annoyingsite1.com http://www.popupsite2.com"); user_pref("capability.policy.popupsites.windowinternal.open","noAccess"); * Or turn it off everywhere: user_pref("capability.policy.default.windowinternal.open","noAccess"); * Override popping up new windows on target=anything: user_pref("browser.target_new_blocked", true); * Override popup windows at beginning of new page load (blocks most popup advertisements): user_pref("dom.disable_open_during_load", true);ACACACCAL: When focus and/or selection changes they are in the viewport CPIOnly allows confirmation if the information is not secure? This is also under Preferences, Security, SSL, "Sending form data from unencrypted page to unencrypted page" PIACAL: * The DOM is available in-process, but not via an out-of-process (COM) interface. * Out-of-process access is needed for it to be truly useful for assistive technology * We do support some COM interfaces called ISimpleDOMNode, which has a large portion of useful DOM read accessACACACAC * The DOM is available in-process, but not via an out-of-process (COM) interface. * Out-of-process access is needed for it to be truly useful for assistive technology * We do support some COM interfaces called ISimpleDOMNode, which has a large portion of useful DOM read access ACACNIAL: Still working on Active Accessibility support for other kinds of content NININRNRNRNRAC * Can use keyboard API to control Mozilla, by generating keystrokes programmatically * When in-process, can use DOM to generate events * Uses Active Accessibility to provide program access to controls * Do not support all Active Accessibility features for programmatic operation (put_accName, put_accValue not yet supported) ACACACCAL: * Uses Active Accessibility to generate change events to assistive technology CCCAL: * Uses standard keyboard API, works with a number of assistive technologiesCNRAL: We use 16 bit strings, not sure about UTF-16NRACAL: * The DOM is available in-process, but not via an out-of-process (COM) interface. * Out-of-process access is needed for it to be truly useful for assistive technology ACACNRAL: Too vague to measure. NRACAL: * Mozilla uses selection colors as specified in the control panel. * Mozilla exposes the focus via WM_FOCUS system messages * Mozilla does not use the system focus drawing routines, because they aren't flexible enough (don't support CSS) ACACAL: * Mozilla implements standard keyboard bindings * There are a few missing pieces, such as support in XUL comboboxes (menulist) for selecting items by typing alphanumeric keystrokes ACPI * Mozilla uses non-native controls. It does, however, support the look and feel of widgets on various operating systems, when the classic theme is selected (on by default). PIPIAL: * Menus indicate accesskey and accelerator configurations * Accelerators not show in button tooltipsPIPIAL: * HTML: CAPTION element (TABLE): Renders in graphical interpretation, can be styled using CSS * HTML: THEAD element (TABLE): Available through DOM, can be styled using CSS? * HTML: TBODY element (TABLE): Available through DOM, can be styled using CSS? * HTML: TFOOT element (TABLE): Available through DOM, can be styled using CSS? * HTML: COLGROUP element (TABLE): Available through DOM, can be styled using CSS? * HTML: COL element (TABLE): Available through DOM, can be styled using CSS? * HTML: SCOPE attribute (TABLE): Available through DOM * HTML: HEADERS attribute (TABLE): Available through DOM * HTML: AXIS attribute (TABLE): Available through DOM * HTML: TABINDEX attribute: yes, can be used to order sequential navigation * HTML: ACCESSKEY attribute: Supported with ALT-{key}, menu key conflict favor the accesskey? * HTML: ALT for IMG: yes * HTML: LONGDESC for IMG: yes, available in context menu properties * HTML: ALT for AREA: ? * HTML: ALT for INPUT: ? * CSS: TEXT-INDENT: yes * CSS: TEXT-ALIGN: yes * CSS: WORD-SPACING: yes * CSS: LETTER-SPACING: yes * CSS: FONT-STRETCH: NI * CSS: MARGIN: yes * CSS: FLOAT: yes * CSS: POSITION: yes * CSS: !IMPORTANT: yes * CSS: SYSTEM FONTS: yes * CSS: SYSTEM COLORS: yes * CSS: list types: yes * CSS: OUTLINE: no * CSS: :before, :after: Poor * CSS: :hover: ? * CSS: :visited, :unvisited: ? PIACAL: * HTML 4.01: VG * CSS2: VG * CSS2: VG * DOM 1.0: VG ACCCCCCPI * Provides sequential access to links and input form controls * Cannot navigate to non-links and non-input form controls with event handlers * Cannot configure Mozilla to only allow focus changes on explicit user request PIPIPINIAL: See bug 36539 NINIPIAL: Can turn off scripting, but then no event processing is available PIPIAL: Can view event handlers through source view or DOM Inspector (Tasks, Tools, DOM Inspector) PIPIPIAL: * Provides sequential access to links and input form controls * Cannot navigate to non-links and non-input form controls with event handlers * No directional navigation, or navigation to links by name PIPICAL: * Provides forward and reverse text search capability from the element with the current focus/selection, with and without case sensitivity * Very slow on larger documents. Needs improvement. CCCCCPIAL: * DOM Inspector provides some capability, but not really intended for end users (Tasks, Tools, DOM Inspector) * Navigation to Links: yes * Navigation to Form controls: yes PICNICNININIPICNICNINININININIPIAL: * We don't make use of scope, headers, axis, or any other table accessibility features * We have nothing under properties, or anywhere else, to orient users reading a table PINRNRCNINININICNRAL: * Provides a focus outline box * Highlights follow graphical rendering conventions for windows * Does not highlight selected images * We do not have the ability to show a border around the text selection * We have the following focus appearance prefs that are not exposed in the UI, but can be manually inserted in the user's prefs.js file: * SetBoolPref("browser.display.use_focus_colors", useFocusColors); /* true or false */ * SetCharPref("browser.display.focus_background_color", colorString); /* for example #ffeedd or the name of a color */ * SetCharPref("browser.display.focus_text_color", colorString); * SetCharPref("browser.display.focus_ring_width", numPixels); /* integer 0-4 */ CCACACACACACAL: * We rely on color alone when showing which links have been recently visited. * Should implement a pref for dotted underline on visited links, similar to the way Opera does it. ACPI * DOM Inspector provides a type of outline view, although it is not intended for end users * Page info (Ctrl+I) gives lists of links, media, forms/elements * Can use a user style sheet to implement an outline * Bug 127030 has been filed for an outline view. NRPIPIPIAL: * Only uses color to indicate whether a link has been visted by default * Context menu properties provides link information, but does not provide the size of the resource. Note that the size might be discovered for certain resources using HTTP HEAD. However, any such use should be carefully considered, given the potential impact on network traffic of automatically making such requests for every link/object in the page. Please see bug 103704 for more information. * Does not provide information about whether link is internal or external, except through URL itself. Clearly identifying internal vs. external links is bug 127038. * Provides information about whether link will open in same window * Does not support fee links PIACAL: * Uses title bar color and focus indicator to indicate with view port has focus * The currently focused content frame has a dotted outline, until a key is pressed or scrolling occurs * The focus appearance is not configurable ACACACACAL: * A progress bar and status bar message indicates loading progress * The scroll bar indicates how far into the document the current graphical view is * The size of the current document is in the page info screen, sometimes it says unavailable ACPIAL: * Menus indicate accesskey and accelerator configurations * Accelerators not show in button tooltips * No centralized key bindings informational resource for end-users, only developer documentation PINIAL: The web page itself is currently responsible for letting the user know what accesskey's are available. NIPIAL: * Some bindings can be changed. See "the customizing document" * There is no central place to change all bindings. Unforutunately, some are hard coded. Needs work. Bug#? PINIAL: Bug 953707 is our open bug for this. Help wanted. NINICCCCCCCPIAL: * User profiles are fully supported for all configuration options. * Unfortunately, switching profiles requires the entire application to be relaunched. * There is still very little end-user documentation for editing profiles by hand. CPIPIAL: * Can turn on and off toolbars under Show/Hide * Can customize personal bookmarks toolbar * Bug 15144 is for the ability to add/remove toolbar icons * Bug 47418 is for the ability to rearrange toolbars PIPIPINRAL: * Some end user docs are under Help, Help Contents in Mozilla * None of documentation resources have been evaluated for WCAG compliance NRNINININININININI