Issues
- CKEditor Return inserts <p>UMICH-734Resolved issue: UMICH-734
- Google analytics script not functioning on mobile portalUMICH-733Resolved issue: UMICH-733Gonzalo Silverio
- Maintain users are unable to see existing files or upload new files to Modules (Melete)UMICH-732Resolved issue: UMICH-732Patrick Haggood
- Upload-Download Multiple Resources instructions need to be updated for OS X 10.8UMICH-731Resolved issue: UMICH-731Chris Kretler
- change "setup.request" setting for production to point to itsm specific group email, instead of ctools@umich.eduUMICH-729Resolved issue: UMICH-729UMich Developers
- Signup Tools does not allow you to remove meetingsUMICH-728Resolved issue: UMICH-728
- Update Copyright tag to 2013UMICH-726Resolved issue: UMICH-726
- Exclude Gradtools from CSRFUMICH-723Resolved issue: UMICH-723Zhen Qian
- Update copyright footer to reflect 2013UMICH-722Resolved issue: UMICH-722Gonzalo Silverio
- Update UMich build and run-time environment to run with Java 7UMICH-719Resolved issue: UMICH-719David Haines
- Update UMich build to run with maven 3UMICH-718Resolved issue: UMICH-718Kent Fitzgerald
- Review/restore indie projects to UM .externals fileUMICH-715Resolved issue: UMICH-715Kent Fitzgerald
- Create web-service to clean up tool properties for Worksite Setup toolUMICH-704UMich Developers
- Install SCORM Player contrib toolUMICH-699Resolved issue: UMICH-699
- patch 2.9 portals (neo and default) for Google linksUMICH-645Resolved issue: UMICH-645Patrick Haggood
- Discussion tool and CSRF protectionUMICH-643Resolved issue: UMICH-643Gonzalo Silverio
CKEditor Return inserts <p>
Description
Details
Assignee
UnassignedUnassignedReporter
John JohnstonJohn JohnstonComponents
Affects versions
Priority
Major
Details
Details
Assignee
Reporter
Components
Affects versions
Priority
MajorActivity
John JohnstonJanuary 16, 2013 at 7:23 AM
OK, we will add the SHIFT+RETURN workaround to the help docs to point disgruntled users to. We could post this as a tip on MOTD also.
Beth KirschnerJanuary 16, 2013 at 6:23 AM
Based on preferences of accessibility and ckeditor optimizations for <p>, I suggest we leave the default behavior as is.
Gonzalo SilverioJanuary 16, 2013 at 5:16 AM
A question posed to the Sakai a11y group:
"A side effect of Michigan's upgrade to 2.9 was the CKEditor's default of separating blocks of text by wrapping them in a <p> instead of separating them with a <br />
The question was raised about a11y ramifications. Is there a preference for one or the other?"
The answers:
Scott Williams (UM): "This change is a good thing, as paragraphs are enclosed in their own semantic elements."
Joe Humbert (IUPUI): "Yes, I agree. Enclosed paragraph tags provide both improved semantics and enhanced navigation. Screen reading software provides a mechanism to jump from paragraph to paragraph."
Additionally:
"Screen readers and search engines do not stop for soft returns in the same way that they do for paragraph endings."
http://www.userite.com/web-accessibility/page-semantics/basic-accessible-page.html
Gonzalo SilverioJanuary 15, 2013 at 12:43 PM
I have done a bit research - found nothing on <p> vs <br /> in the a11y context. But the top level guidelines encourage semantic markup whenever possible.
Sean Michael DemonnerJanuary 15, 2013 at 12:37 PM
Which would have the least negative impact on promoting the creation of accessible content?
Hitting RETURN in the CKEditor results in inserting a paragraph <p> instead of a break <br> (behavior in 2.7).
Suggest setting default behavior to return a line break, as this is what users are used to. I believe this can be accomplished by setting the "Format" attribute of the editor to "Normal(Div)"
Work around for users is to use SHIFT+RETURN
Reported in ITSM ticket: REQ000000203370