AO3 News

Post Header

2014-11-02 09:39:14 -0500


  • Coders: Emily, Enigel, james_, sarken
  • Code reviewers: Ariana, Enigel, james_, Scott
  • Testers: Lady Oscar, mumble, Runt, Scott


  • The option to remove requests or offers while filling in a challenge sign-up wasn't working when there were required tag fields on the sign-up form. Now it works again.
  • There was some old bookmark code hanging around, not doing anything. Now it's gone.
  • The "Bookmark External Work" button was available to visitors on the bookmark listings for tags. Only logged-in users can create bookmarks, so we removed the button.
  • When browsing your subscriptions page on mobile devices with small screens, the links for accessing only series, user, or work subscriptions weren't working when tapped. Now they work.
  • The little tooltip pop-up for the header's search field (suggesting possible keywords and sort options) only worked for users navigating by mouse or trackpad. Now it will work for people using keyboards, screen readers, or touch screens as well. Additionally, now it only appears when the search field is selected, rather than popping up whenever the cursor is nearby.
  • We used an HTML attribute to label many things in various listings on the site -- for example, the titles of works. Unfortunately, some screen readers read the content of this attribute instead of the actual text, which made it sound like every work on the Archive was named "Title." We've removed this attribute from everywhere it could impact screenreaders in this way.
  • When an admin went to a user's dashboard, any restricted works the user had posted were hidden from the admin. Now the admin can access those works from the user's dashboard, just like regular logged-in users can.
  • We moved to an even stronger encryption method for safely storing passwords.
  • Previewing a work for the first time automatically creates a draft. However, subsequent previews don't update that draft unless the user explicitly chooses "Save Without Posting". We removed the message that implied otherwise. Remember, don't use our posting form as your only writing tool! Browsers can crash, things can go wrong, your draft might get eaten. Always have a backup somewhere else.
  • We considerably spruced up the README file used for displaying information about the AO3 software project on

Known Issues

See our Known Issues page for current issues.