WordPress.org

Make WordPress Accessible

Updates from January, 2014 Toggle Comment Threads | Keyboard Shortcuts

  • Joseph Karr O'Connor 5:36 am on January 25, 2014 Permalink
    Tags: , ,   

    Accessibility Team Update: January 22, 2014 

    Ticket Activity Report

    @grahamarmfield reported progress on ticket 26602: Insufficient information for screen readers in themes.php. “On the new Themes page in trunk, it is now possible to tab to each of the themes within the list of themes found. However for screen readers there may be no audible feedback to tell the user which theme has focus.” Thanks to @joedolson for the initial patch and everyone else who worked on the solution. The status is now: closed defect (bug) (fixed).

    Keyboard Testing

    Some of us are proceeding with the keyboard functionality audit of all the admin screens. We have a target deadline of February 5, 2014 to complete the testing. There is a learning curve as each team member learns the routines. Some of us have never done testing so this is a valuable learning experience for us. We are comparing our findings before making them public. @rianrietveld has made a test instance available to us so that we are all using the same environment. She also posted about this on our WordPress Accessibility LinkedIn group. Thanks to everyone who is participating.

     

     
  • Joseph Karr O'Connor 7:57 pm on January 17, 2014 Permalink
    Tags: , ,   

    Accessibility Team Meeting January 15, 2014 

    Testing 3.8 Admin Screens

    The team discussed our current project, keyboard testing of 3.8 admin screens. There is now a new page on Make WordPress Accessible named Testing, and a sub-page under that named 3.8 Admin Screens Results. The testing page contains a list of 3.8 admin screens and a sample results table. The results page contains the report we are starting to build. We agreed on a testing methodology and the WCAG 2.0 AA success criteria we will reference. Testing is now underway.

    Other Projects

    • During the meeting @jorbin notified us that #26602 is ready for testing after he applied a patch.
    • Also @davidakennedy is still committed to helping out the Widgets project and @grahamarmfield is going to have a look at the AH-O2 plugin which is now on the repo.
    • At the same time we are checking the admin screens for keyboard accessibility we will also be doing a separate report on all WCAG 2.0 AA issues on the P2 Theme we are using for this blog.
     
  • Rian Rietveld 6:38 pm on January 17, 2014 Permalink  

    3.8 Admin screens testing results 

    Keyboard Functionality Test Results

    Test Guide

    Page Name Goes Here
    # Issue Standard Severity Recommendation
    1 Keyboard All functionality of the content is operable through a keyboard interface. 2.1.1 High, Med, Good
    2 No Keyboard Trap Ensure that content does not “trap” keyboard focus within subsections. 2.1.2
    3 Bypass Blocks A mechanism is available to bypass blocks of content that are repeated on multiple Web pages. 2.4.1
    4 Focus Order When users navigate sequentially through content make sure they encounter information in an order that is consistent with the meaning of the content. 2.4.3
    5 Focus Visible Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible. 2.4.7
    6 On Focus When any component receives focus, it does not initiate a change of context. 3.2.1

    Good = passed test
    Med = some inconvenience
    High = showstopper

    Toolbar

    1. Skip Link (control, visible when using keyboard)
    # Issue Standard Severity Recommendation
    1.1 Bypass Blocks – First tab in page invokes skip links menu. “Skip to Main Content” and “Skip to toolbar” are options, but not “Log Out.” The Log Out option comes after the Log Out menu item at the end of the Toolbar which is confusing. 2.4.1 Med Place “Log Out” skip links option under “Skip to Main Content” and “Skip to toolbar” in main skip links menu. Users of assistive technology (AT) can quickly move cursor to top of page, invoke the skip links menu, and select Log Out easily.

    Toolbar

    2. Toolbar Itself
    # Issue Standard Severity Recommendation
    2.1 Keyboard – In the dropdown menu under “Howdy, [username]” the first item [username] is skipped. The next item “Edit My Profile” has same link as [username]. (Two different menu items with same link destination contravenes 3.2.4 Consistent Identification.) The last item of the dropdown menu under “Howdy, username” is Log Out. One tab stop further the same “Log Out” link pops up as a skip link which is confusing. 2.1.1 Med Do not bypass [username] in tab order. Place “Log Out” skip link in main skip link menu.

    Toolbar

    3. WordPress (icon) – About WordPress – What’s New, Credits, Freedoms tabs
    # Issue Standard Severity Recommendation
    1 Keyboard 2.1.1 Med
    2 No Keyboard Trap 2.1.2
    3 Bypass Blocks 2.4.1
    4 Focus Order 2.4.3
    5 Focus Visible 2.4.7
    6 On Focus 3.2.1

    Toolbar

    4. Comments (icon)
    # Issue Standard Severity Recommendation
    1 Keyboard 2.1.1 High, Med, Good
    2 No Keyboard Trap 2.1.2
    3 Bypass Blocks 2.4.1
    4 Focus Order 2.4.3
    5 Focus Visible 2.4.7
    6 On Focus 3.2.1

    Toolbar

    5. Add New Post – Add Media – Edit Media – Media Library
    # Issue Standard Severity Recommendation
    5.1 Keyboard – Help Screen – links in the help-tab content can not be reached by keyboard only. Edit Media – The options for cropping, rotation and flipping are skipped. These options become visible when selecting “Edit Image.” Cropping an image is not possible for a keyboard-only user. Rotating and flipping are not available. 2.1.1 Med Help Screen – make help-tab links keyboard controllable. Edit Media – cropping, rotating, and flipping should be keyboard controllable.
    5.2 No Keyboard Trap – Set Featured Image – Can close the popup by entering the escape key but this is not apparent to user. Add New Post – Tabbing beyond “Set Featured Image” gets the tab order back to the underlying screen, but the focus does not return to “Set Featured Image” popup. 2.1.2 Med Set featured image – visually add “Esc” in front of X. Add New Post – “Set Featured Image” keyboard control should always be available.
    5.3 Focus Order – Add Media – “add a file” link still an option in the multi-file uploader mode. Media Library – Taborder in the main table runs through table head, table foot, table body. In long table tabbing to table foot scrolls screen way down which may be confusing. 2.4.3 Med Add Media – “add a file” link should be skipped in the multi-file uploader mode. Media Library – change tab order to table head, table body, table footer.
    5.4 Focus Visible – Add New Post – Radiobuttons have no visible focus. Dropdown, Checkbox, Screen Options, and Help menus have insufficient visible focus.
    Set Featured Image popup window: The items Upload files and Media Library, select Files and Set Featured image, don’t have a (or just a little) visible focus. Keeps you guessing where you are, especially because the tab order leaves the popup after tabbing beyond “Set Featured Image”. Add Media – link for adding a file with “browser’s built-in file uploader” is not visible so there’s one extra tab with no visible action after tabbing the “try the browser uploader” link.
    2.4.7 Med Add New Post – Add or increase visible focus to all keyboard accessible links and controls. Add Media – add focus to all keyboard accessible links and controls.

    Customize Page

    /customize.php
    # Issue Standard Severity Recommendation
    x.1 Focus Visible The Active Theme area has no focus indicator. Color blocks underneath color square have a focus indicator, but because of the border radius, it’s hard to see. The No Image selector in the Background Image area has no focus indicator. Focus indication on radio buttons in the overall section is weak. Collapse label does not have focus indicator. 2.4.7 High Standardize visible focus indicators according to types of controls and links selected by keyboard users.

    Toolbar

    page name
    # Issue Standard Severity Recommendation
    1 Keyboard 2.1.1 High, Med, Good
    2 No Keyboard Trap 2.1.2
    3 Bypass Blocks 2.4.1
    4 Focus Order 2.4.3
    5 Focus Visible 2.4.7
    6 On Focus 3.2.1

    Toolbar

    page name
    # Issue Standard Severity Recommendation
    1 Keyboard 2.1.1 High, Med, Good
    2 No Keyboard Trap 2.1.2
    3 Bypass Blocks 2.4.1
    4 Focus Order 2.4.3
    5 Focus Visible 2.4.7
    6 On Focus 3.2.1

    Toolbar

    page name
    # Issue Standard Severity Recommendation
    1 Keyboard 2.1.1 High, Med, Good
    2 No Keyboard Trap 2.1.2
    3 Bypass Blocks 2.4.1
    4 Focus Order 2.4.3
    5 Focus Visible 2.4.7
    6 On Focus 3.2.1

    Left Navigation

    Pages – All Pages
    # Issue Standard Severity Recommendation
    1 Keyboard 2.1.1 High, Med, Good
    2 No Keyboard Trap 2.1.2
    3 Bypass Blocks 2.4.1
    4 Focus Order 2.4.3
    5 Focus Visible 2.4.7
    6 On Focus 3.2.1

    Left Navigation

    Pages – New Pages
    # Issue Standard Severity Recommendation
    x.1 Keyboard the controls of TinyMCE are unavailable to the keyboard user in Visual mode and available in Text mode, but only by shift tabbing backwards out of the content entry field. Shift tabbing out of the content entry field deselects any text the user might have wanted to act on with the controls, so the controls are partly useless. When the “link” control is invoked a modal dialog box is then available. The “Escape” key does not dismiss this modal dialog box, instead there is a control marked “cancel.” 2.1.1 High, Med, Good Suggest that all TinyMCE controls be keyboard controllable in Visual and Text mode. Some means of preserving selection in content text field while keyboarding to select controls should be devised. All modal dialog boxes, regardless of other controls to dismiss, should also be controllable with the “Escape” key.
    2 No Keyboard Trap 2.1.2
    3 Bypass Blocks 2.4.1
    4 Focus Order 2.4.3
    5 Focus Visible 2.4.7
    6 On Focus 3.2.1

    Left Navigation

    Comments
    # Issue Standard Severity Recommendation
    x.1 Keyboard When returning to the ‘main’ Comments screen after using the Quick Edit panel, the quick links under each comment (eg Unapprove, Reply, etc) no longer appear when tabbing through that particular comment. They do however appear for the other comments which is good. When adding a link into comment in Quick Edit, the ‘Insert/Edit link’ panel appears with focus on the first field. It does not appear to be possible to tab to the ‘Or link to existing content’ ‘link’ so it can’t be actioned by keyboard only. Actioning this with a mouse extends the panel to allow search on a term. The search input field can get focus, but the various options shown when search criteria are entered cannot get focus so keyboard selection of one is not possible. 2.1.1 High, Med, Good
    x.2 Focus Order When forward tabbing, the extra links for each comment appear and you can tab to them. However when reverse tabbing from the post title in right hand column, the links become visible but they are not now in the tab order. 2.4.3 Medium
    x.3 Focus Visible When tabbing forwards, focus disappears after Filter button. It’s actually on the select all checkbox. Visible focus is weak. After actioning Quick Edit link, an editor window appears with focus clearly in text editor input. Reverse tabbing from here takes you to all of the various formatting ‘buttons’ – eg bold, italic, link, etc but focus is not at all visible when it rests on each of these buttons in turn. When actioning the Spam or Trash links, the comment is replaced by a ‘marked as spam’, ‘moved to trash’ message and an ‘Undo’ link. But focus has now apparently disappeared. Further tabbing shows it’s in the right area. 2.4.7 High

    Left Navigation

    Comments Edit Page
    # Issue Standard Severity Recommendation
    x.1 Keyboard When adding a link into comment, the ‘Insert/Edit link’ panel appears with focus on the first field. It does not appear to be possible to tab to the ‘Or link to existing content’ ‘link’ so it can’t be actioned by keyboard only. Actioning this with a mouse extends the panel to allow search on a term. The search input field can get focus, but the various options shown when search criteria are entered also cannot get focus so keyboard selection of one is not possible. 2.1.1 High
    x.2 Focus Visible Formatting and link buttons, focus is not at all visible.
    Focus not visible when user is keyboard interacting with Approved, Pending and Spam radio buttons in Status box.
    When you first action Edit link to set submitted date of comment, the focus disappears at first but does reappear when you continue tabbing.
    2.4.7 High

    Left Navigation

    Appearance – Widgets
    # Issue Standard Severity Recommendation
    x.1 Focus Visible The Screen Options and Help Tabs near the top of the page have a visible focus state, but it is hard to notice. The radio buttons in “Add” page of Widgets process have a weak focus state. The “Add” button on the widgets has a focus state (the traditional dotted outline), but the hover state is stronger (light on dark colors). 2.4.7 Screen Options and Help Tabs need more than a drop shadow around the links. Radio buttons in “Add” page of Widgets process need a stronger focus state. Suggest alignment of keyboard and visual focus indicators on “Add” button.
    Appearance – Menu’s
    # Issue Standard Severity Recommendation
    x.1 Keyboard 2.1.1 Good
    x.2 No Keyboard Trap 2.1.2 Good
    x.3 Bypass Blocks 2.4.1 n/a
    x.4 Focus Order 2.4.3 Good
    x.5 Focus Visible
    See also the 5.4 remarks about radio buttons / checkboxes / screen options and help. In the menu-settings-column (pages/post/links etc) the focus is visible by a change in background color of the div. In post-body (Menu Structure) the focus is visible only by a change of colour of the arrow on the right of the div.
    2.4.7 Med
    1. Improve the contrast difference of the background colour on focus in menu-settings-column
    2. Improve the contrast difference of the arrow colour on focus in menu-settings-column
    3. Or better: let the focus of the two act the same in a clearly way
    6 On Focus 3.2.1 Good
    Appearance – Header
    # Issue Standard Severity Recommendation
    x.1 Keyboard
    Select Image: “Choose Image from your media library” gets no focus and is skipped.
    Header Text: When this option is selected, under Preview the site name gets focus but it isn’t clickable, that doesn’t work with a mouse either, and it’s done on purpose.
    Why is this done? ( onclick=return false ) Seems confusing.(No remark, but a compliment) Header Text -> Text color: Sliders and colour selection works perfectly with keyboard only, very neat!

    After uploading an image:
    Crop header image: Is not possible with the keyboard (alternative?)

    2.1.1 High Remove keyboard focus on Header Text link to site site
    Give a keyboard accessible way to crop an image after uploading.
    Add focus on the Select image -> choose image from media library.
    x.2 No Keyboard Trap 2.1.2 Good
    x.3 Bypass Blocks 2.4.1 n/a
    x.4 Focus Order 2.4.3 Good
    x.5 Focus Visible
    See 5.4 remarks about radio buttons/checkboxes/screen options and help
    Header Text -> Text color: Focus on the boxes with the colours below the colour selection is hardly visible.
    2.4.7 Med Provide better focus on the boxes with the colours below the colour selection.
    x.6 On Focus 3.2.1 Good
    Appearance – Background
    # Issue Standard Severity Recommendation
    x.1 Keyboard
    Select Image: “Choose Image from your media library” gets no focus and is skipped.
    2.1.1 High Add focus on the Select image -> choose image from media library
    x.2 No Keyboard Trap 2.1.2 Good
    x.3 Bypass Blocks 2.4.1 n/a
    x.4 Focus Order 2.4.3 Good
    x.5 Focus Visible
    See 5.4 remarks about radio buttons/checkboxes/screen options and help
    Header Text -> Text color: Focus on the boxes with the colours below the colour selection is hardly visible.
    2.4.7 Med Provide better focus on the boxes with the colours below the colour selection.
    x.6 On Focus 3.2.1 Good
    Appearance – Editor (same as Plugins – Editor)
    # Issue Standard Severity Recommendation
    x.1 Keyboard 2.1.1 Good
    x.2 No Keyboard Trap
    After tabbing inside the textarea you can’t tab out because the tab is added to the content. In the help the solution for this is given: “In the editing area the Tab key enters a tab character. To move below this area by pressing Tab, press the Esc key followed by the Tab key”. This took me quite a while to find out (yeah yeah RTFM).
    2.1.2 Good
    x.3 Bypass Blocks 2.4.1 n/a
    x.4 Focus Order 2.4.3 Med It would be nice if there was a way to skip all the files after selecting one and jump straight into the textarea to edit the file selected.
    x.5 Focus Visible. 2.4.7 Good
    x.6 On Focus 3.2.1 Good

     

    Users

    profile.php
    # Issue Standard Severity Recommendation
    1 Keyboard 2.1.1
    2 No Keyboard Trap 2.1.2
    3 Bypass Blocks 2.4.1
    4 Focus Order 2.4.3
    5 Focus Visible 2.4.7
    6 When clicking on “skip to content” the your profile page shifts upwards (css issue). 3.2.1  Medium  ** This error occurs on all pages that are longer than the browser height. Recommendation: if #wpbody-content had margin-top:-32px;padding-top:32px the jump would not occur (32px is the height of the admin bar)

     

    Tools

    profile.php
    # Issue Standard Severity Recommendation
    1 Keyboard 2.1.1
    2 No Keyboard Trap 2.1.2
    3 Bypass Blocks 2.4.1
    4 When an “install plugin” pop up window appears when pressing ENTER on the import list links, the focus starts from the import tab in the left menu, then you have to either “skip to content” or “skip to toolbar” to continue. In both scenarios, the pop up window is last on the keyboard tabbing flow; although the ESC key does close the window. 2.4.3  Medium  When an ‘install plugin’ popup appears, #tb_overlay and #tb_window are being appended to the body. Having #tb_overlay and #tb_window prepended to the body instead would eliminate this issue.
    5 Focus Visible 2.4.7
    6
    On Focus
    3.2.1

     

    Settings

    options-general.php
    # Issue Standard Severity Recommendation
    1 When tabbing through the various options, when the user gets to “date format” and “time format” on tab to “custom” it gets selected instead of selectable. 2.1.1 Medium  *Currently if a user focuses on the textbox under the ‘DATE FORMAT’ section for the ‘Custom’ option, the custom radio option is automatically selected, this should be changed to only automatically select the ‘Custom’ option, if the textbox value is actually changed.
    2 No Keyboard Trap 2.1.2
    3 Bypass Blocks 2.4.1
    4 Focus Order 2.4.3
    5 Focus Visible 2.4.7
    6 When the user clicks on “skip to content” the page shifts upward. 3.2.1  ** This error occurs on all pages that are longer than the browser height. Recommendation: if #wpbody-content had margin-top:-32px;padding-top:32px the jump would not occur (32px is the height of the admin bar)

     

    Settings

    options-writing.php
    # Issue Standard Severity Recommendation
    1 Keyboard 2.1.1
    2 No Keyboard Trap 2.1.2
    3 Bypass Blocks 2.4.1
    4 Focus Order 2.4.3
    5 Focus Visible 2.4.7
    6 When the user clicks on “skip to content” the page shifts upward. 3.2.1  Medium ** This error occurs on all pages that are longer than the browser height. Recommendation: if #wpbody-content had margin-top:-32px;padding-top:32px the jump would not occur (32px is the height of the admin bar)

     

    Settings

    options-discussion.php
    # Issue Standard Severity Recommendation
    1 Keyboard 2.1.1
    2 No Keyboard Trap 2.1.2
    3 Bypass Blocks 2.4.1
    4 Focus Order 2.4.3
    5 Focus Visible 2.4.7
    6 When the user clicks on “skip to content” the page shifts upward. 3.2.1  Medium  ** This error occurs on all pages that are longer than the browser height. Recommendation: if #wpbody-content had margin-top:-32px;padding-top:32px the jump would not occur (32px is the height of the admin bar)

     

    Settings

    options-permalink.php
    # Issue Standard Severity Recommendation
    1 When tabbing through this section, when the user tabs to “custom structure” is selects it instead of making it selectable. 2.1.1  Medium  *Currently if a user focuses on the textbox under the ‘COMMON SETTINGS’ section for the ‘Custom Structure’ option, the custom radio option is automatically selected, this should be changed to only automatically select the ‘Custom’ option, if the textbox value is actually changed.
    2 No Keyboard Trap 2.1.2
    3 Bypass Blocks 2.4.1
    4 Focus Order 2.4.3
    5 Focus Visible 2.4.7
    6 3.2.1
     
  • Joseph Karr O'Connor 10:04 am on January 11, 2014 Permalink
    Tags: , ,   

    IRC Meeting: January 8, 2014 

    Workflow Redux

    In 1982, in his Frank and Ernest comic strip, Bob Thaves wrote about Fred Astaire: “Sure he was great, but don’t forget that Ginger Rogers did everything he did, backwards…and in high heels.”

    Doing the accessibility dance is very much like that. Great care is taken to make sure that not only do we produce useful reports and code solutions but that whatever we create is as accessible as possible. For instance, last week we stated that when we produce word processing documents, they will be output as RTF, to preserve formatting between platforms. We also said we’d use Dropbox because it integrates so tightly with operating systems, giving our team access to files while using assistive technology in familiar ways. Using Dropbox as a staging area for documentation and automatically pushing finished work, including code solutions, to Github seemed like a good way to make our work public. The good is often the enemy of the best.

    WordPress

    This week we discussed this blog and how we can best integrate our workflow into the WordPress environment. Remember when Drupal set up a WordPress blog to publish info about Drupal? Perhaps we should explore our workflow options within our own ecosystem. This week we started working through the issues we face when contemplating using WordPress to publish our findings.

    Tables

    Mostly all of the accessibility assessments I’ve worked with, both manual and automatic, contain tables to display issues, reference to guidelines, solutions, etc. It might not be absolutely necessary to display this info in tables, but tables sure help to organize this type of tabular data. We just need to code accessible tables in WordPress. You can read how to properly code tables in Creating Accessible Tables by WebAIM.

    TinyMCE and Tables

    WordPress ships with a WYSIWYG editor, TinyMCE. TinyMCE has a table tool. The TinyMCE site does have a page devoted to TinyMCE accessibility with one brief reference to tables. We’d have to test both the back end functionality and the output of that tool before we can say that it can be easily used with a keyboard and that it outputs accessible table code. If we need to, we’ll work with the Meta team to devise an accessible table feature for TinyMCE and it will benefit more than our project.

    P2 Template

    This page is produced using the P2 Theme. When it comes down to it, if we really want to make sure that our output is accessible, then we should check the P2 Theme for accessibility. This also will benefit more than our project alone.

    Action Items

    At the end of the meeting we summed up our next actions to work within WordPress to publish our accessibility findings accessibly, and to proceed with our focus on keyboard accessibility of admin pages:

    1. Check TinyMCE table tool function and output, work with the Meta team if needed
    2. Check P2 Theme for accessibility
    3. Proceed with keyboard functionality assessment of admin pages
     
    • pjries16 2:31 pm on January 11, 2014 Permalink | Log in to Reply

      The TinyMCE table tool does allow you to mark up header cells, scope, caption, summary and add thread and body elements. Part of the challenge is that these are handled by several different icons in the table tool – table properties, row properties and cell properties. I have been using this for a number of years. It’s included in the TinyMCE Advanced plugin. I haven’t tested the accessibility of the tool from a backend perspective, but I do know that it offers those features, if that helps.

    • Joseph Karr O'Connor 6:12 pm on January 11, 2014 Permalink | Log in to Reply

      Thanks pjries16 for telling us about this TinyMCE functionality. I know that backend accessibility is a feature of TinyMCE so it will be interesting to test this out.

  • Joseph Karr O'Connor 4:49 am on January 2, 2014 Permalink
    Tags: , ,   

    IRC Meeting: January 1, 2014 

    Happy New Year to the entire WordPress community!

    Accessible IRC Clients

    Thanks to the team members who joined us today, and to @grahamarmfield who reported in while traveling. Just as we got underway we had a question on Twitter asking which IRC clients are accessible plus we found out later that one of our team members, @arush was sidelined when her IRC client “totally choked.” So after the meeting we used the LazyWeb technique and asked @WPAccessibility followers for some suggestions:

    Much thanks to Jennifer, who is a big help to the accessibility team and to the entire accessibility community, and also thanks to Chris Nestrud for the Unix suggestion. Chris says: “anything with a text UI on Unix should work. I like irssi.” We can still use suggestions for accessible IRC clients for iOS, Android, and Windows Mobile.

    Workflow

    We are starting the process of auditing 3.8 for keyboard accessibility. Reports are generated in the process of accessibility auditing. We discussed how to handle those reports. A few meetings ago @ceo suggested that we create the reports in RTF format so the formatting is not lost in the platform shuffle and we will do that.

    During today’s meeting we finalized plans to create a public Github repository where we will store the finished reports and other documents as we produce them. We will also create and update our assignments and to-do lists on Github.

    We also finalized plans to create a Dropbox account for the team which we will use to store documents to be reviewed before they are finalized. Tom Harrigan made the suggestion that we set up a directory in Dropbox that will automatically sync from dropbox to github.

    @davidakennedy has agreed to set up Github and Dropbox. Thanks David!

     
    • ceo 5:20 am on January 2, 2014 Permalink | Log in to Reply

      Sounds like it was a very productive meeting! I really like the Dropbox-Github syncing; that should prove quite useful.

    • Joseph Karr O'Connor 5:25 am on January 2, 2014 Permalink | Log in to Reply

      @ceo yes, it was a very productive meeting. Thanks for your RTF suggestion. Dropbox will give us a very familiar interface. Automatic posting to Github will help those unfamiliar with it.

    • Jen Mylo 11:35 pm on January 2, 2014 Permalink | Log in to Reply

      Is there any way your docs could be created/stored somewhere in the wordpress.org setup rather than using third-party services? Could you describe what features you require that we can’t accommodate internally? That would be helpful, so that if there are tools that we should be looking into having here, we’ll know what to consider.

c
compose new post
j
next post/next comment
k
previous post/previous comment
r
reply
e
edit
o
show/hide comments
t
go to top
l
go to login
h
show/hide help
shift + esc
cancel
Skip to toolbar