Clarification of accessibility

4 posts, 0 answers
  1. Nathan J Pledger
    Nathan J Pledger avatar
    95 posts
    Member since:
    Apr 2006

    Posted 03 Nov 2010 Link to this post

    I am reading up on the accessibility of the RadEditor control.

    On ms-help://telerik.aspnetajax.radcontrols.2010.Q1/telerik.aspnetajax.radeditor.2010.Q1/standards-compliance-and-browser-support.html

    Can you please clarify what this means:

    Accessibility - Telerik RadEditor satisfies the requirements for accessibility, which is a result of the following:
    - the interface of the Telerik RadEditor is "Level A" accessible (in accordance with the W3C Web Accessibility Guidelines 1.0).
    - the content generated by the Telerik RadEditor can become accessible if the author fills in all required fields (marked with a special accessibility icon  ). 
      

    Assuming that users fulfil the requirements of accessibility (identified by the symbol), what level of accessibility (A, AA, AAA) does the editor output? What settings are required to achieve this?

    Update: to be clear, I'm asking about the generated mark-up from the user via the editor, not the editor UI itself.
  2. Rumen
    Admin
    Rumen avatar
    12849 posts

    Posted 08 Nov 2010 Link to this post

    Hi Nathan,

    RadEditor provides the needed tools and documentation for produce accessible content , but it does not validate the content or enforce the user to create such content. RadEditor includes additional fields in the Table, Hyperlink and Image dialogs.  You can find detailed information about how to produce accessible content using RadEditor in the Creating Accessible Content section of the help.

    We are also working with HiSoftware on providing a new Accessibility Validator dialog for RadEditor. If you are interested in, you can contact their support and learn more about this new feature.

    Best regards,
    Rumen
    the Telerik team
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
  3. UI for ASP.NET Ajax is Ready for VS 2017
  4. Nathan J Pledger
    Nathan J Pledger avatar
    95 posts
    Member since:
    Apr 2006

    Posted 08 Nov 2010 Link to this post

    Hi Rumen,

    Thanks for your reply. I appreciate your assertion that it is ultimately up to the user to create accessible content, but we are after a black or white answer in order to respond to a client. "Accessible content" could mean "A", but we need "AA". 

    Given that:
    • Users are effectively trained up to complete the appropriate fields in an accessible manner (as you say, completing dialogs correctly)
    • The editor is suitably configured
    • The emitted content will be rendered within a AA Accessible surrounding page

    Does the editor emit content that is suitable for "AA" validation? 

    Thanks also for the link for the Validator partner. This would help assert upon the user that it is ultimately *their* responsibility to produce accessible content. No black-boxes are possible.
  5. Rumen
    Admin
    Rumen avatar
    12849 posts

    Posted 10 Nov 2010 Link to this post

    Hi Nathan J Pledger,

    We do not claim that the content produced by RadEditor passes the "AA" validation, but the RadEditor's tools could provide the ability to create such content. For example you can use the RadEditor's brand new Compliance Check dialog (the last button on the toolbar) to validate the content. My suggestion is to test the new tool and contact the guys from HiSoftware for more information about your specific requirements.

    Greetings,
    Rumen
    the Telerik team
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
Back to Top