We have a brand new look! Take a tour with us and explore the latest updates on Adobe Support Community.
While I started reading for "Customizable HTML5 Indigo Layout" to see if it is 508 compliant, I noticed this term, "chrome-less" (indicated in red below). I'm copying text from the Adobe RoboHelp Online Help:
Present a visually rich content to your audience by using the chrome-less HTML5 Indigo layout. The Indigo layout is built in accordance with the latest web design trends and combine a striking look with unmatched functionality. It is a 508 compliant layout designed to create content for users with special needs and also offer superior search and intuitive navigation experience."
Does this mean, 508 compliance will be unavailable on Chrome browser? I wanted to confirm before I tell this to my stakeholders.
I'm not Adobe, of course, and I have no clue how much of what you shared is just considered marketing hype. But generally speaking, when you visit a web site using a web browser, that browser has "chrome". (not to be confused with the Google Chrome browser).
Chrome consists of things like presenting a title bar, and an address bar, and a status bar and other elements. So typically, when you have a "chromeless" window, those elements are missing.
I believe what you copied also says that whatever is being done is actually meeting 508 compliancy standards.
Hopefully someone from Adobe will pop in to clarify.
Thank you so much Rick! I'll apply this out and see how the display works.
Jakob Nielsen gives a comprehensive explanation here, as well as pros and cons of chrome and how it applies to usability. I admit I'd never heard the term 'chrome' used in conjunction with websites before.
On a website, the chrome includes navigation bars, footers, logos, branding, the search box, and so forth.
The problem I have with the use of the term "chromeless" here is that originally it meant content that displayed without the browser menu and toolbar, as Rick has explained. You saw just the help content and its toolbar. I believe it was partly a design thing and partly so that users could not substitute another address and browse, done where companies would not allow users access to a browser.
I don't see how the term can be used in the context you have shown.
As to 508 compliance, you would need to check your version and the skin being used with Adobe. Bear in mind that whilst a skin might be compliant, your content also has to be and Adobe have no control over that. The use of colours is affected, for example.
Where did you find the text you have quoted?
See www.grainge.org for free RoboHelp and Authoring information.
Thank you Peter! I found the text in RoboHelp's Online Help.
As you said:
"As to 508 compliance, you would need to check your version and the skin being used with Adobe. Bear in mind that whilst a skin might be compliant, your content also has to be and Adobe have no control over that. The use of colours is affected, for example."
Where can I get more information or learn on how I can make my content 508 compliant?
Thanks in advance!