Navigation Mobile

System Limitations

System Limitations


User1st systems are web-based platform that provides a non-invasive, quick-deploy solution to enhance the compliance of your Section 508 and Web Content Accessibility Guidelines (WCAG 2.0 AA) accessibility needs. Use1st provides a platform to facilitate all aspects of a successful web-accessibility compliance program. User1st’s Detect/Fix/Deploy model combines User1sts powerful detection engine and User1sts Automation System, which allows User1st customers to remediate their existing web pages with no coding required.


Use1st’s follows the W3C standards which includes: a. WCAG techniques and other guidance for designers and developers through the Mobile Accessibility Task Force, including Mobile Accessibility: How WCAG 2.0 and Other W3C/WAI Guidelines Apply to Mobile. b. WAI-ARIA (Accessible Rich Internet Applications) – See the WAI-ARIA Overview


The configuration of a website components through the User1st back-end editor mapping process.


  1. Client – an owner of webpage that is using User1st system to provide accessibility to his users, a client may use an integration party that will perform under the client terms
  2. User – a person that uses webpage, that is User1st system to provide accessibility
  3. User1st system – All User1st’s proposed technologies
  4. Web Accessibility – refers to the inclusive practice of removing barriers that prevent interaction with, or access to websites, by people with disabilities. When sites are correctly designed, developed and edited, all end users shall have equal access to information and functionality.
  5. Screen Reader –  is Assistive Technology, which can read out, using synthesized speech, either selected elements of what is being displayed on the monitor (helpful for end users with reading or learning difficulties), or which can read out everything that is happening on the computer (used by blind and vision impaired end users).
  6. Assistive Technology is an umbrella term that includes assistive, adaptive, and rehabilitative devices for people with disabilities and also includes the process used in selecting, locating, and using them.
  7. A Disability Profile is a functional description of what accommodation is being requested by the end user without needing to identify their disability which could create privacy concerns. For example: a color blind person would request a “monochromatic” profile, a person suffering Parkinson’s or other motor function would select “key board navigation” or a combination of several.  These preferences are saved so they do not need to be initiated by the end user more than once
  8. The User1st Code Fix plug-in is a testing and configuration tool for advanced business analysts with a background in HTML, Web Accessibility, and a subset of JQuery Selectors
  9. User1st Accessibility Error Detection shall detect machine-detectable WCAG (Web Content Accessibility Guidelines) AA level compliance within a browser at run time.
  10. software snippet – is a Javascript code, creating the accessibility button, the accessibility menu and downloading the site scripts per each disability profile request
  11. Hybrid on premise integration – is when the client integrate some of User1st system (beyond the software snippet) over the client’s servers, in such a case the customer will be responsible for data and software backup, and for reconstruction if necessary.

Software and Hardware

  • Hardware Support – No hardware support is required as along as the solution is provided as a cloud-based .
  • Software Development/Support – User1st is responsible for software maintenance only, unless it is specified otherwise. Software maintenance services will be delivered after inspection of a 2nd level support.

System Requirements

  1. User1st Editor / Code Fix plug-in
    1. Microsoft – Firefox Browsers latest version
    2. Fiddler – latest version
  2. User1st Front End
    1. Desktop – MS: Firefox, Chrome, Explorer version, iOS latest Safari latest
    2. Mobile: iOs Safari latest version, Android Chrome latest version
  3. Screen readers
    1. Desktop – MS:Firefox combined with NVDA, Internet Explorer combined with JAWS
    2. Desktop and Desktop iOs: Safari combined with VoiceOver
    3. Mobile Android: Chrome combined with Talkback
  4. Software snippet, must be placed at the top of the of the <HEAD> tag, also in iFrames and Frames, while each Frame must have a unique ID
  5. The client may design the accessibility button. Verizon is responsible for placing the accessibility button and the accessibility statement in a clearly visible place on the website, including the pages of the website.
  6. User1st system is activated after the page loads, when a user has selected a feature or a profile or clicked over user1st activation button
  7. For the purpose of compliance and maintenance, the client is responsible for any textual substitute for non-textual content on the website (such as flash files, picture files, graphs, tables, etc.). The client is responsible for any file, which is not HTML, such as PDF, and Office files, and creation of captions for any short film with words, which are spoken, in the short film or audio.
  8. User1st recommends the client to be supported by an audit i.e. an accessibility authority/expert in order to obtain a high level of assurance that accessibility is logical for disabled users. In these audits the audit party performing the audit carries out an examination with use of the keyboard only, use of a screen reader and an examination of the color settings and links required by the standard. In addition, the audit must be on all the pages of the website / app functionalities. While the User1st software is not a substitute for an audit body of accessibility authorities/experts it to be used for making the website accessible in accordance with the Web Content Accessibility Guidelines (WCAG) 2.0.
  9. The client is responsible for updating the configurations or mappings when their website code changes at the minimum once a year, in case of hybrid on premise integration.
  10. All requirements of the law, which are not supported by User1st’s system, will have to be dealt with by the client (See “The system does not support”). Work in accordance with the “Requirements and limitations of the system” appendix is an integral part of the client’s obligations”.
  11.  All requirements of the law, which are not supported by User1st’s system, will have to be dealt with by the client (See “The system does not support”). Work in accordance with the “Requirements and limitations of the system” appendix is an integral part of the client’s obligations”.
  12. The client is responsible for any or all textual substitute alternative text for non-textual content on the website, such as flash files, picture files, headers, graphs and data tables.

System General Limitations

  1. User1st systems are provided AS IS, special elements that are not supported by User1st software, can be develop under special terms, and aren’t part of these terms. Due to the dynamic nature of websites and online content, new issues, features, capabilities, support that will be required from User1st to be provided, following the initial integration of User1st system, will be subject to additional terms defined by User1st.
  2. User1st systems are bounded to User1st End User License Agreement.
  3. The User1st systems supports HTML files and HTML tags only
  4. Unless it is specified otherwise, User1st will not be responsible for accessibility training or for the quality of the integration/application of the system or for any action concerning use which is not in accordance with the software company’s specifications and documentation, which are contrary to the standardization and requirements of web accessibility compliance defined by W3.
  5. User1st system does not design the website
  6. User1st screen reader functionality is bounded and limited by the combination the Operating System, Screen Readers or/and Browsers. User1st will always try to work around these issues when possible but are frequently blocked by the browser and operating system support of the ATAG standards. Below are some examples (not a fully enumerated list) of known bugs or limitations in operating systems and screen readers:
    • On Mobile Devices:
      • Android Talkback fails to create a click event on Firefox browser,
      • Android talkback fails to focus on elements that are not on the screen viewport
      • All mobile screen readers (iOS and Android) fail to focus properly on elements that need to have a keyboard entry and a selection done on the same time
      • All mobile screen readers may fail to focus while the mobile screen keyboard is active

    • On Desktop:
      • JAWS and NVDA fail in most of the aria tags on chrome
      • JAWS has known issues assessing the label tag, due to heavy JAWS heuristics
      • NVDA is likely to fail in many scenarios over Internet Explorer.
  7. 3rd level party components included in User1st enabled sites by the customer, are not supported by the standard User1st license agreement due to the dynamic nature of content. User1st can support these types of situations under special terms, and aren’t part of this agreement. Third party software is integrated into the products, which are provided by User1st, the customer undertakes full responsibility for these third party products with respect to User1st functionality. Customers may still only use User1st software it in accordance with the license agreement and all other terms and conditions.

HTML Limitations

User1st system may be required as part of the provision of accessibility in order to meet the standard, but will fail to support the following, therefore are not warrantied under this agreement:


  1. User1st systems does not support or support partially the compliance of files type as: FLEX, FLASH, Silverlight, Applets, PDF, Microsoft Office, media players, the creation of film or audio captions, and the support for tags which do not reveal the source of the file, such as: <canvas>, dynamically loaded SVG or in CAPTCHA files, as well User1st will not support controlled session created at the server level.Dragging a component on the screen, e.g. drag and drop, in such cases the client will have to create an alternative button, which replaces the dragging functionality.
  2. User1st leverages technologies that its content “relies upon” including: XHTML 1.0 Transitional, CSS 2.0 and JavaScript 1.2 which may not be available in older browsers.
  3. User1st limitations may be JavaScript contradictions existing in the client’s website as if they deliberately block keyboard control, or which create a loop, e.g. misuse of <input> or <SELECT> tags, or scroll blocking at the time of use with a keyboard, e.g. single page applications.
  4. Components that their code and content are contradictory in meaning, e.g. as a button on which “purchase” is written in code and on the display/design “sale” is written.
  5. Components which have an orientation in virtual space without an indication in code as to their location or as to a unique characteristic in them or as to their functionality, e.g as a map, interactive graphs.
  6. Tables made up of <DIV> tags, where the lines of content are not wrapped in single unique tag and ID, or in components which can be functionally understood only by virtue of their content which is based on location, size or colour.
  7. Pages with over one hundred (100) pictures or heavy use of Javascript, may cause performance issues when leveraging the software.
  8. User1st system do not change the code order so that it will be logical in order to present the information systematically to end users of screen readers, and a change of page structure for those components may be required.
  9. User1st system may fail in automatic identify components and the client may be require to add addition of “Class” to the HTML components on the site may be required.
  10. User1st system may fail in detecting the page language, and will require support from the client in identifying the language on the page
  11. User1st may fails to support <Frameset> tags, However, upon assessment and specific agreement with User1st <Frameset> can be supported, while any Frame must have a source and dialog and frames will not be generated on the client side

Mobile devices limitations:

User1st is only supported on adaptive or responsive pages, i.e sites that automatically adapt to fit the mobile size, page weight, and scrolling.

Want to learn more about website accessibility? Save your seat for our latest webinar!