Bug 769411 - 508 Compliance, Frames
Summary: 508 Compliance, Frames
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss Operations Network
Classification: JBoss
Component: 508
Version: JON 3.1.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: JON 4.0.0
Assignee: RHQ Project Maintainer
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks: 769382
TreeView+ depends on / blocked
 
Reported: 2011-12-20 18:43 UTC by Mike Foley
Modified: 2019-06-24 14:53 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-06-24 14:53:37 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
5 (1.04 MB, application/pdf)
2011-12-20 18:43 UTC, Mike Foley
no flags Details

Description Mike Foley 2011-12-20 18:43:28 UTC
Created attachment 548923 [details]
5

194.22 (i) Frames

Provision
Frames shall be titled with text that facilitates frame identification and
navigation.

Plain English
Frames must be clearly identified so users understand their purpose and
contents.

Compliance may be achieved by defining attributes in the tags that
generate the frames, or simply by text content in each document visible
inside frames.

Why this is important.
Frames are an additional challenge to navigate for users with special
needs: They effectively creating multiple separate HTML documents within
the same browser window. The purpose or content for each frame must
be clearly identified in text for users of assistive technologies to navigate
through the frames effectively.

Section 508 Compliant?
Not Compliant

What must be fixed?
Frames lack a meaningful and descriptive title that would provide
screen reader users with an understanding of each frame’s content.

See pages 32-39 of attached document

Comment 1 Mike Foley 2012-01-23 16:27:02 UTC
setting priority to medium per bz triage crouch, foley, loleary

Comment 2 Filip Brychta 2019-06-24 14:53:37 UTC
JBoss ON is coming to the end of its product life cycle. For more information regarding this transition, see https://access.redhat.com/articles/3827121.
This bug report/request is being closed. If you feel this issue should not be closed or requires further review, please create a new bug report against the latest supported JBoss ON 3.3 version.


Note You need to log in before you can comment on or make changes to this bug.