<!— a single H1 in the page here —>
<h2>service / portlet 1</h2>
<p>bla bla bla</p>
<h2>service / portlet 2</h2>
<h2>service / portlet 3</h2>
TAMU has surfaced that a best practice is to have H1s to separate major content for accessibility. uPortal should use H1s for tabs.
This change is can potentially break some css in Custom skins. It should be rather simple to find and correct the CSS, however.
So should we make this change in a patch release, enhancement, or wait for uP6?
Benito J. Gonzalez
Senior Software Developer
Email: [hidden email]
You received this message because you are subscribed to the Google Groups "uPortal Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/uportal-dev/32EDDE6B-3E60-41FF-80E9-2706E1423C05%40unicon.net.