Date:
|
6/27/16
|
Name of Product:
|
Microsoft® FrontPage® 2003
|
Contact for more Information:
|
http://www.microsoft.com/frontpage http://www.microsoft.com/enable
|
Summary Table
Section 508 Voluntary Product Accessibility Template
Criteria
|
Supporting Features
|
Remarks and explanations
|
Section 1194.21 Software Applications and Operating Systems
|
Supported. Please refer to the attached VPAT
|
|
Section 1194.22 Web-based internet information and applications
|
Supported. Please refer to the attached VPAT
|
|
Section 1194.23 Telecommunications Products
|
|
Microsoft FrontPage 2003 is not considered a telecommunications product.
|
Section 1194.24 Video and Multi-media Products
|
|
Microsoft FrontPage 2003 does not use multimedia except as covered in section 1194.21
|
Section 1194.25 Self-Contained, Closed Products
|
|
Microsoft FrontPage 2003 is not a self-contained product.
|
Section 1194.26 Desktop and Portable Computers
|
|
Microsoft FrontPage 2003 is software as defined under section 1194.21
|
Section 1194.31 Functional Performance Criteria
|
Supported. Please refer to the attached VPAT
|
|
Section 1194.41 (a) Information, Documentation and Support
|
Supported. Please refer to the attached VPAT
|
|
Section 1194.21 Software Applications and Operating Systems - Detail
Section 508 Voluntary Product Accessibility Template
Criteria
|
Supporting Features
|
Remarks and explanations
|
(a) When software is designed to run on a system that has a keyboard, product functions shall be executable from a keyboard where the function itself or the result of performing a function can be discerned textually.
|
Supported with minor exceptions:
Microsoft FrontPage 2003 supports Microsoft Windows accessibility features including StickyKeys, FilterKeys, MouseKeys, High Contrast and more.
Keyboard access is provided throughout Microsoft FrontPage version 2003. Keyboard shortcuts, shortcut keys, and menu commands are readily available in FrontPage 2003.
FrontPage 2003 Help functionality includes easily accessible reference guides for keyboard accessibility.
FrontPage 2003 applications do not require speech recognition; however, Microsoft FrontPage 2003 includes speech recognition as a supplementary input and control mechanism. This feature allows an individual to dictate text, make direct formatting changes and navigate menus using speech and voice commands input by microphone.
FrontPage 2003 speech recognition is available in the Simplified Chinese, English (U.S.), and Japanese language versions of Microsoft FrontPage version 2003.
|
Accessibility limitations occur when using freehand drawing tools and other minor exceptions including limited keyboard access in the Theme Preview dialog window.
|
(b) Applications shall not disrupt or disable activated features of other products that are identified as accessibility features, where those features are developed and documented according to industry standards. Applications also shall not disrupt or disable activated features of any operating system that are identified as accessibility features where the application programming interface for those accessibility features has been documented by the manufacturer of the operating system and is available to the product developer.
|
Supported with minor exceptions:
FrontPage 2003 supports the accessibility settings of the operating system.
FrontPage 2003 does not disrupt or disable any accessibility features of the operating system.
FrontPage 2003 enables individuals to customize their desktop elements, including resizing and rearranging toolbars and menus, choosing color, size, sound, and format options.
FrontPage 2003 supports large fonts in the title bar, toolbars and most dialogs and FrontPage 2003 fully supports operating system accessibility features including StickyKeys, FilterKeys, MouseKeys, High Contrast and more.
|
Exceptions are features that do not support large font settings or high contrast settings. These features are documented in 1194.21(g).
|
(c) A well-defined on-screen indication of the current focus shall be provided that moves among interactive interface elements as the input focus changes. The focus shall be programmatically exposed so that Assistive Technology can track focus and focus changes.
|
Supported with minor exceptions:
Microsoft FrontPage 2003 supports technologies that make computer programs more accessible to people who use Assistive Technology. Visual on-screen focus and tracking is provided throughout FrontPage 2003.
|
FrontPage 2003 supports Microsoft Active Accessibility (MSAA) and the system caret in all instances with some minor exceptions in inconsistent or loss of focus when using the keyboard to navigate the User Interface (UI) when editing list field properties and document libraries properties settings dialogs in a Microsoft Windows® SharePoint™ Services-based Web site or while using the Photo Gallery Properties dialog in FrontPage.
|
(d) Sufficient information about a user interface element including the identity, operation and state of the element shall be available to Assistive Technology. When an image represents a program element, the information conveyed by the image must also be available in text.
|
Supported with minor exceptions:
Microsoft FrontPage 2003 User Interface elements include menu bars, toolbars, check boxes and buttons, to name a few.
Microsoft FrontPage 2003 supports active accessibility programming interfaces as well as the Microsoft Office Object Model which is available to individuals to access the user interface. In addition, FrontPage has its own publicly documented Object Model that covers areas that are not core Office. This enables 3rd party software developers to produce accessibility related products as add-ins specifically for FrontPage.
|
FrontPage 2003 supports MSAA for all user interface elements with certain exceptions including the Microsoft Script Editor (a tool embedded in FrontPage 2003) and limited information conveyed about some UI elements such as certain properties dialogs, dropdown list boxes, and web bots as well as the Lookup field properties dropdown menu when editing Windows SharePoint Services-based Web sites.
|
(e) When bitmap images are used to identify controls, status indicators, or other programmatic elements, the meaning assigned to those images shall be consistent throughout an application's performance.
|
Supported:
Microsoft FrontPage 2003 utilizes standard and consistent images throughout FrontPage 2003. All images used for controls or programmatic elements are consistent throughout the FrontPage 2003 applications.
|
|
(f) Textual information shall be provided through operating system functions for displaying text. The minimum information that shall be made available is text content, text input caret location, and text attributes.
|
Supported:
Microsoft FrontPage 2003 uses standard system functions to send textual information to the operating system in all cases.
|
|
(g) Applications shall not override user selected contrast and color selections and other individual display attributes.
|
Supported with minor exceptions:
FrontPage 2003 supports large fonts in the title bar, toolbars, and in some dialogs. FrontPage 2003 does not extend operating system user defined font settings to the document frame due to the need to preserve the WYSIWYG (What You See is What You Get) User Interface (UI) model. However, FrontPage 2003 does enable the user to set document font sizes according to their specific needs.
|
FrontPage 2003 does not support large font mode in dialogs where large fonts would render the dialog impossible to read. The operating system magnifier application is available to magnify dialog text.
FrontPage 2003 does not fully support high contrast mode when viewing SharePoint Services Web Parts in Design and Split views. However, high contrast mode for viewing Web Parts is supported in Preview and HTML view.
Other minor exceptions include inconsistent or unsupported application of user selected font or contrast settings in certain views and view panes.
|
(h) When animation is displayed, the information shall be displayable in at least one non-animated presentation mode at the option of the user.
|
Supported:
FrontPage 2003 does not use animation to display critical information to the user. Our user assistance does include some animations but the information conveyed via animation is always available elsewhere in the user assistance model.
Microsoft FrontPage 2003 includes some animated objects such as the animated Office Assistant used with Help. Animation can be turned on or off at the individual user’s discretion. In FrontPage 2003, in all instances, equal access to the same information is provided in a non-animated mode.
|
|
(i) Color coding shall not be used as the only means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.
|
Supported with minor exceptions:
Microsoft FrontPage 2003, with few exceptions, does not use color to convey information. FrontPage 2003 applications that use color to convey information also use an alternate means to convey the same information.
|
|
(j) When a product permits a user to adjust color and contrast settings, a variety of color selections capable of producing a range of contrast levels shall be provided.
|
Supported:
A minimum of eight colors selections are provided in all instances where Microsoft FrontPage 2003 allows a user to select from a range of colors.
FrontPage 2003 supports operating system settings for high contrast color schemes that make the screen easier to view for some users by heightening screen contrast with alternate color combinations.
|
|
(k) Software shall not use flashing or blinking text, objects, or other elements having a flash or blink frequency greater than 2 Hz and lower than 55 Hz.
|
Supported:
Microsoft FrontPage 2003 does not use flashing or blinking objects or text in any application User Interface.
|
|
(l) When electronic forms are used, the form shall allow people using Assistive Technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues.
|
Supported:
FrontPage 2003 forms are accessible to people using Assistive Technology.
|
|
Section 1194.22 Web-based Internet Information and Applications - Detail
Section 508 Voluntary Product Accessibility Template
It is incumbent upon users of FrontPage to acquire the knowledge and develop appropriate procedures to create accessible Web sites To help users of FrontPage create accessible Web sites, Microsoft provides a number of resources including the following Web sites:
http://www.microsoft.com/frontpage/using/accessibility/default.htm
http://www.microsoft.com/enable/
Criteria
|
Supporting Features
|
Remarks and explanations
|
(a) A text equivalent for every non-text element shall be provided (e.g., via "alt", "longdesc", or in element content).
|
Supported:
Microsoft FrontPage 2003 includes functionality that makes it possible to create pages within FrontPage 2003 that conform to this criterion. FrontPage 2003 users are responsible for ensuring that their own Web pages conform to this criterion.
|
|
(b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation.
|
Supported:
Microsoft FrontPage 2003 includes functionality that makes it possible to create pages within FrontPage 2003 that conform to this criterion. FrontPage 2003 users are responsible for ensuring that their own Web pages conform to this criterion.
|
|
(c) Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup.
|
Supported:
Microsoft FrontPage 2003 includes functionality that makes it possible to create pages within FrontPage 2003 that conform to this criterion. FrontPage 2003 users are responsible for ensuring that their own Web pages conform to this criterion.
|
|
(d) Documents shall be organized so they are readable without requiring an associated style sheet.
|
Supported:
Microsoft FrontPage 2003 includes functionality that makes it possible to create pages within FrontPage 2003 that conform to this criterion. FrontPage 2003 users are responsible for ensuring that their own Web pages conform to this criterion.
|
|
(e) Redundant text links shall be provided for each active region of a server-side image map.
|
Supported:
Microsoft FrontPage 2003 includes functionality that makes it possible to create pages within FrontPage 2003 that conform to this criterion. FrontPage 2003 generated image maps are client-side. FrontPage 2003 users are responsible for ensuring that their own Web pages conform to this criterion.
|
|
(f) Client-side image maps shall be provided instead of server-side image maps except where the regions cannot be defined with an available geometric shape.
|
Supported:
Microsoft FrontPage 2003 includes functionality that makes it possible to create pages within FrontPage 2003 that conform to this criterion. FrontPage 2003 generated image maps are client-side. FrontPage 2003 users are responsible for ensuring that their own Web pages conform to this criterion.
|
|
(g) Row and column headers shall be identified for data tables.
|
Supported:
Microsoft FrontPage 2003 includes functionality that makes it possible to create pages within FrontPage 2003 that conform to this criterion. FrontPage 2003 users are responsible for ensuring that their own Web pages conform to this criterion.
|
|
(h) Markup shall be used to associate data cells and header cells for data tables that have two or more logical levels of row or column headers.
|
Supported:
Microsoft FrontPage 2003 includes functionality that makes it possible to create pages within FrontPage 2003 that conform to this criterion. FrontPage 2003 users are responsible for ensuring that their own Web pages conform to this criterion.
|
|
(i) Frames shall be titled with text that facilitates frame identification and navigation
|
Supported:
Microsoft FrontPage 2003 includes functionality that makes it possible to create pages within FrontPage 2003 that conform to this criterion. FrontPage 2003 users are responsible for ensuring that their own Web pages conform to this criterion.
|
|
(j) Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz.
|
Supported:
Microsoft FrontPage 2003 includes functionality that makes it possible to create pages within FrontPage 2003 that conform to this criterion. FrontPage 2003 users are responsible for ensuring that their own Web pages conform to this criterion.
|
|
(k) A text-only page, with equivalent information or functionality, shall be provided to make a web site comply with the provisions of this part, when compliance cannot be accomplished in any other way. The content of the text-only page shall be updated whenever the primary page changes.
|
Supported:
Microsoft FrontPage 2003 includes functionality that makes it possible to create pages within FrontPage 2003 that conform to this criterion. FrontPage 2003 users are responsible for ensuring that their own Web pages conform to this criterion.
|
|
(l) When pages utilize scripting languages to display content, or to create interface elements, the information provided by the script shall be identified with functional text that can be read by Assistive Technology.
|
Supported:
Microsoft FrontPage 2003 includes functionality that makes it possible to create pages within FrontPage 2003 that conform to this criterion. FrontPage 2003 users are responsible for ensuring that their own Web pages conform to this criterion.
|
|
(m) When a web page requires that an applet, plug-in or other application be present on the client system to interpret page content, the page must provide a link to a plug-in or applet that complies with §1194.21(a) through (l).
|
Supported:
Microsoft FrontPage 2003 includes functionality that makes it possible to create pages within FrontPage 2003 that conform to this criterion. FrontPage 2003 users are responsible for ensuring that their own Web pages conform to this criterion.
|
|
(n) When electronic forms are designed to be completed on-line, the form shall allow people using Assistive Technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues.
|
Supported:
Microsoft FrontPage 2003 includes functionality that makes it possible to create pages within FrontPage 2003 that conform to this criterion. FrontPage 2003 users are responsible for ensuring that their own Web pages conform to this criterion.
|
|
(o) A method shall be provided that permits users to skip repetitive navigation links.
|
Supported:
Microsoft FrontPage 2003 includes functionality that makes it possible to create pages within FrontPage 2003 that conform to this criterion. FrontPage 2003 users are responsible for ensuring that their own Web pages conform to this criterion.
|
|
(p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required.
|
Supported:
Microsoft FrontPage 2003 does not require the user to respond with a specified time for any operations. FrontPage 2003 includes functionality that makes it possible to create pages within FrontPage 2003 that conform to this criterion. FrontPage 2003 users are responsible for ensuring that their own Web pages conform to this criterion.
|
|
Section 1194.31 Functional Performance Criteria - Detail
Section 508 Voluntary Product Accessibility Template
Criteria
|
Supporting Features
|
Remarks and explanations
|
(a) Vision: At least one mode of operation and information retrieval that does not require user vision shall be provided, or support for assistive technology used by people who are blind or visually impaired shall be provided.
|
Supported with minor exceptions:
Microsoft FrontPage 2003 supports technologies that make computer programs more accessible to people who use Assistive Technology. FrontPage 2003 supports the use of screen readers to access user interface information.
FrontPage 2003 supports the use of screen readers that use MSAA or the object model to access user interface information.
|
Commonly-used Assistive Technology may be used with these products. Users of AT should contact their AT vendor to assess the compatibility of their product with Microsoft products and to learn how to adjust their settings to optimize interoperability.*
Minor exceptions include: formatting-type smart tags which are activated by a user hovering over text using a keyboard or mouse. The hover action enables screen readers to use the smart tag shortcut (Alt+Shift+F10) to open the smart tag menu. The menu that appears is accessible through the keyboard.
Identical functionality is provided through standard FrontPage 2002 toolbar options.
|
(b) Visual acuity: At least one mode of operation and information retrieval that does not require visual acuity great than 20/70 shall be provided in audio and enlarged print output working together or independently, or support for assistive technology used by people who are visually impaired shall be provided.
|
Supported with minor exceptions:
Microsoft FrontPage 2003 supports the use of screen readers to access user interface information.
FrontPage 2003, with few exceptions, also supports system large font settings.
|
Minor exceptions noted in section 1194.21.
Users of Microsoft Windows operating systems can access Magnifier in the Accessibility Options in the Control Panel. A 3rd party Assistive Technology may also be used. *
|
(c) Hearing: At least one mode of operation and information retrieval that does not require user hearing shall be provided, or support for assistive technology used by people who are deaf or hard of hearing shall be provided.
|
Supported:
Microsoft FrontPage 2003 does not require user hearing for access to any Office application functionality. In all instances where FrontPage 2003 provides an audio cue, FrontPage 2003 provides a visual cue as well.
FrontPage 2003 does not require user hearing for access to any of its functionality. In all cases that FrontPage 2003 provides an audio cue, FrontPage 2003 provides a visual cue as well.
|
|
(d)Audio Information: Where audio information is important for the use of a product, at least one mode of operation and information retrieval shall be provided in an enhanced auditory fashion, or support for assistive hearing devices shall be provided.
|
Supported:
Microsoft FrontPage 2003 does not require user hearing for access to any Office application functionality. In all instances where FrontPage 2003 provides an audio cue, FrontPage 2003 provides a visual cue as well.
|
Volume controls are available through the Windows operating system. In addition, a 3rd party Assistive Technology may be used1
|
(e) Speech: At least one mode of operation and information retrieval that does not require user speech shall be provided, or support for assistive technology used by people with disabilities shall be provided.
|
Supported:
FrontPage 2003 applications do not require speech recognition.
Microsoft FrontPage 2003 includes speech recognition as a supplementary input and control mechanism. This feature allows an individual to dictate text, make direct formatting changes and navigate menus using speech and voice commands input by microphone. Unlike a full end-to-end speech recognition stand-alone product, the feature itself cannot be initially activated by speech; it requires keyboard or mouse input to start the operation.
FrontPage does not require user speech for any functionality save for our speech recognition features. Speech recognition is not required to access any information contained within FrontPage 2003.
|
|
(f) Motor Skills/Coordination: At least one mode of operation and information retrieval that does not require fine motor control or simultaneous actions and that is operable with limited reach and strength shall be provided.
|
Supported:
Microsoft FrontPage 2003 supports operating system tools such as StickyKeys and FilterKeys as well as other Assistive Technologies.
When the StickyKeys feature is on, the user can press a modifier key (SHIFT, CTRL, or ALT) and then another key in sequence rather than at the same time, to enter shifted (modified) characters and other key combinations. Pressing a modifier key once latches the key down until the user presses a non-modifier key or clicks a mouse button. Pressing a modifier key twice locks the key until the user presses the key a third time.
The FilterKeys accessibility feature allows the user to set the keyboard repeat rate, acceptance delay and bounce rate.
|
FrontPage supports operating system tools such as StickyKeys and FilterKeys, as well as assistive technology that supports MSAA (save for the exceptions noted in 1194.21).
|
*Note to AT Users: Upon the release of software upgrades, there is often a lag between the software release date and the time it takes for some Assistive Technology manufacturers to upgrade their software and device drivers to support these new releases. The manufacturer’s porting timeframe may be a factor in determining when you decide to upgrade to take advantage of new features. Microsoft provides the software code within its products to make our products "ready" for the AT devices and works closely with major AT providers in an effort to decrease the time to market for new versions of AT products. We encourage both end users and purchasers of AT to contact their AT manufacturer to determine the current compatibility of their existing AT with Microsoft products.
Section 1194.41 Information, Documentation, and Support - Detail
Section 508 Voluntary Product Accessibility Template
Criteria
|
Supporting Features
|
Remarks and explanations
|
Section 1194.41 (a) Product Support Documentation
|
Supported
|
Documentation is provided in digital format for customers on the web and available for no-charge download at http://microsoft.com/office/downloads
This documentation is completely accessible using Internet Explorer 5.0 or above, which is required for use with FrontPage 2003.
|
Section 1194.41 (b) Accessibility and Compatibility Features
|
Supported
|
Microsoft FrontPage 2003 product documentation includes a top-level link to ‘Accessibility Information’ and ‘Keyboard Shortcuts.’ This documentation is also available in the free, downloadable documentation discussed above.
|
1194.41 (c) Support Services
|
Supported
|
The Microsoft Product Support Services Help Desk is familiar with such features as keyboard access and other options important to people with disabilities.
Microsoft offers a teletypewriter (TTY) service for customers who are hearing impaired. For assistance in the United States, contact Microsoft Technical Support on a TTY at 1-800-892-5234. This service is available Monday through Friday 5:00 A.M. to 9:00 P.M. and 5:00 A.M. to 3:00 P.M. Saturday PST.
For information on additional support services, visit the Microsoft Accessibility Web site at http://www.microsoft.com/enable/products/support.aspx
|
This document is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS DOCUMENT.
© 2003 Microsoft Corporation. All rights reserved. Microsoft, FrontPage, Office, Active Accessibility, SharePoint, Windows, and the Windows logo are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. The names of actual companies and products mentioned herein may be the trademarks of their respective owners. The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication.
Revised 6/27/2016 Microsoft regularly updates its websites and provides new information about the accessibility of products as that information becomes available.
|
Yüklə 114 Kb.